Manoj Srivastava writes: > If packages were to include a du -S output (unlike the du -s > output included by some helper packages before), this script, a > modification of Kai' script, could be used to gather the data. This > has yet to be discussed and passed into policy.
Ah, we finally have a use for this data ;) However, I would strongly advise not to use a standalone file like old .du files and .md5sums: the largest part of these files is occupied by the filenames, which are already profided by .list files. I'd suggest that we evolve towards a new generic control-file (say package.fileinfo), that will possibly evolve with time, as need for new/alternate info arise. As an example, it could look like: ==== # name:md5sum:size /a/file:236d8059a2244a31aacc8e127e86f5c0:1234 /another/file:236d8059a2244a31aacc8e127e86f5c0:5678 ==== In my example, the 1st lines defines what info is contained in the file. As policy will be involved, it would maybe be more interesting to list a file-format-version number on this 1st line. Comments, anyone ? -- Yann Dirson <[EMAIL PROTECTED]> | Stop making M$-Bill richer & richer, alt-email: <[EMAIL PROTECTED]> | support Debian GNU/Linux: debian-email: <[EMAIL PROTECTED]> | more powerful, more stable ! http://www.a2points.com/homepage/3475232 | Check <http://www.debian.org/>
