> Ok, that's a doable option, though it'll be a lot simpler to just make a > script that traverses the archive, examines every .deb file, pulls the du > infomation out of them and generates the master file. That doesn't require > modifying every package and adding yet another file that must be uploaded > (and aren't byhand files installed by hand?)
This could be done along with the contents scan, it would take a bit of coding to do as you would have to also implement caching and probably a custom tar reader.. > But how is putting the info in this master file any better than putting it > in Packages? The master file needs to be kept synced with the Packages file, > so it still must be downloaded. Probably because nobody is ever going to download it? :> I can see it interesting some people but not everyone. Besides, putting it seperate means we can maintainer the format of the packages file without undo complication. APT already has a nice mechanism to download multiple index files (ie the Release files). Jason
