Re: On adding size info to Packages files [very long]
- To: Manoj Srivastava <email@example.com>, Brederlow <firstname.lastname@example.org>
- Cc: Charles Briscoe-Smith <email@example.com>, firstname.lastname@example.org, email@example.com, Raul Miller <firstname.lastname@example.org>
- Subject: Re: On adding size info to Packages files [very long]
- From: Joey Hess <email@example.com>
- Date: Thu, 4 Jun 1998 23:49:22 -0400
- Message-id: <19980604234922.B885@kitenet.net>
- Mail-followup-to: Manoj Srivastava <firstname.lastname@example.org>, Brederlow <email@example.com>, Charles Briscoe-Smith <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, Raul Miller <email@example.com>
- In-reply-to: <firstname.lastname@example.org>; from Manoj Srivastava on Wed, Jun 03, 1998 at 09:19:47AM -0500
- References: <199806021535.QAA26278@pcsw104b.ukc.ac.uk> <email@example.com> <firstname.lastname@example.org> <email@example.com>
Manoj Srivastava wrote:
> Brederlow> The size file should be generated by the server. Here are
> Brederlow> the reasons:
> I am (perhaps unnecessarily) worried about time requirements
Considering that we plan to eventually have lintian run automatically on
packages before they get moved into the debian archives, and lintian unpacks
each package itself, there's not much reason to worry about time. Running
lintian on master is going to take longer than generating the du files. And
if time does become a big concern, we could generate the du files from the
lintian lab or something.
> Brederlow> 3. Maintainer will forget to include a du index or have different
> Brederlow> block sizes.
> This can be made policy and a lintian check. We have to trust
> the maintainers a trifle ;-)
How is it possible to check for block sizes with lintian? And what do you
expect a maintainer to do if they use a different block size and lintian
dislikes that? Reformat?
see shy jo
I'm on a long trip, pardon any delays in my reply.
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com