[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#37999: du -S'ing the archive (was: Re: weekly policy summary)



> 
> Date:    Fri, 06 Aug 1999 19:18:32 MDT
> To:      debian-policy@lists.debian.org
> cc:      Debian Policy List <debian-policy@lists.debian.org>
> From:    Jason Gunthorpe <jgg@ualberta.ca>
> Subject: Re: Bug#37999: du -S'ing the archive (was: Re: weekly policy summary)
>
> On Sat, 7 Aug 1999, Anthony Towns wrote:
> 
> > The discussion in the bug report seems to have reached the conclusion
> > that this can be handled simply by modifications to dinstall and apt
> > (or other dselect methods as applicable): that is, to have dinstall
> > generate a DiskUsage.gz file along with Packages.gz or some such and
> > have apt handle it, without any modification to any existing packages,
> > and hence policy. As such, perhaps this should be reassigned as a wishlist
> > bug against ftp.debian.org and apt?
> 
> Could we try not to make policy that mandates something that cannot be
> readily implemented? It is kind of silly to make something policy that
> nobody is going to actually implement.

Agreed in principle, but why is nobody going to implement it? If no one
will do the work, then no one wants to see it done.

> Somebody should sit down and write all the scripts and modifications
> needed before trying to mandate this with policy - besides a disk usage
> index does not really strike me as something belonging in the policy
> domain.

If this is to be done by adding to how packages are made, it
definitely belongs in policy, because ALL packages would then have to
adhere to it. But if there is a way to offer disk usage information
about packages without altering packages, probably the wishlist bug
would work. Do we also need to know if all the other developers want
this done too?

-Jim

---
Jim Lynch       Finger for pgp key
as Laney College CIS admin:  jim@laney.edu   http://www.laney.edu/~jim/
as Debian developer:         jwl@debian.org  http://www.debian.org/~jwl/


Reply to: