Hi,
>>"Richard" == Richard Braakman <[EMAIL PROTECTED]> writes:
Richard> Is a pregenerated du file necessary? You already assume
Richard> that you have the package at hand, so you might as well
Richard> collect size information from the package directly. That
Richard> way, you can also handle differences in block sizes. And it
Richard> means that you don't have to change every package.
Two reasons:
a) The dus file shan't only be in the .deb package. I would like to
add a by hand kind of directive that would upload the
packag_ver.dus file separately, which can then be used to
generate a master .dus file (when last tested, the size of the
file was about 100k). Now, apt can download that file, and one can
know a priori what the size is, without having to download the
package itself.
I would be very annoyed to download the xbooks package over a
28.8 modem, only to learn I can't install it.
b) Our upgrade install process is slow enough already not to add an
additional time consuming extract step (I am willing to be
persuaded otherwise on this issue).
manoj
--
You will have long and healthy life.
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.debian.org/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
