On Mon, Jun 23, 2008 at 12:34 PM, David Rosenstrauch <darose@xxxxxxxxxx> wrote: > Aaron Griffin wrote: >> >> On Mon, Jun 23, 2008 at 11:27 AM, David Rosenstrauch <darose@xxxxxxxxxx> >> wrote: >>> >>> David Rosenstrauch wrote: >>>> >>>> Used to be that when viewing a package's info on the Arch web site that >>>> there was a link to click on that would take you to a page that would >>>> list >>>> the files contained in that package. (i.e., equivalent to the output of >>>> "pacman -Ql <package>") Seems like that functionality is gone now >>>> though. >>>> >>>> Just wondering if there was any particular reason why it was removed, >>>> and >>>> if there were any plans to bring it back. I used to find it a very >>>> handy >>>> tool, and it would be great to have it again. >>>> >>>> Thanks, >>>> >>>> DR >>> >>> Anybody? Beuller? Beuller? :-) >> >> We changed the way the backend worked and parsed information. Due to >> this, it made producing file lists very time consuming. That was the >> only downside for all the many many upsides of changing it that way. >> >> We could still save this data, especially considering Pierre wrote a >> script to generate file lists in the repos themselves[1] but we >> haven't gotten around to it. >> >> 1: ftp://ftp.archlinux.org/extra/os/i686/extra.files.tar.gz > > It'd be nice to have, though not crucial. It's helpful to be able to see > the contents of a package without installing it. Yeah, you may want to post a bug to the tracker, and we can give it off to Dusty, as he's taken over the Django work. If you feel like being sassy and patching some python, the reporead.py script (in the archweb_dev git repo) is the script which parses the db.tar.gz file and inserts things into the DB. It's not that much of a stretch to have this parse the new files.tar.gz files as well and insert THAT info, though I do not know if the DB still contains the tables for package contents.
