Re: Getting rid of circular dependencies
- To: email@example.com
- Subject: Re: Getting rid of circular dependencies
- From: Goswin von Brederlow <firstname.lastname@example.org>
- Date: Mon, 04 Jul 2005 10:48:15 +0200
- Message-id: <[🔎] email@example.com>
- In-reply-to: <20050624183639.GA2429@master.debian.org> (Bill Allombert's message of "Fri, 24 Jun 2005 13:36:39 -0500")
- References: <20050624152151.GQ19190@seventeen> <firstname.lastname@example.org> <20050624155746.GA13115@adrinael.net> <20050624163615.GP2832@p12n.org> <Pine.LNX.email@example.com> <20050624183639.GA2429@master.debian.org>
Bill Allombert <firstname.lastname@example.org> writes:
> On Fri, Jun 24, 2005 at 07:39:16PM +0200, Santiago Vila wrote:
>> Perhaps we should just move to section libs any package which is
>> useless by itself, and it's only useful in combination with others,
>> much like libraries, but without requiring them to be real libraries.
> Good idea. Or we could have a new section for architecture independant data.
> Moving everything which is not mean to be directly installed by users
> in it, so the section games only contains actual games and not the data
Let me suggest obsoleting sections altogether and getting debtags more
firmly placed into the project. Sections are too limited for the
amount of packages in debian.
E.g. xemacs needs to be in editors, x11, web, news, games and mail
But that doesn't realy solve the problem on its own. It would be nice
if packages could be consistently taged with "Application:
yes|no|<untaged>" signifying that this package is usefull on its own
(foo), will never be used alone (foo-data, libfoo) or is
ambigious. Frontends should then hide anything with "Application: no"
under normal operations.
I'm wondering if popcon data could be used to see how many users have
package foo installed without anything depending on foo.