Re: [gentoo-dev] A new category scheme idea

[Vitaly Kushneriuk]

On Mon, 2002-02-04 at 13:25, gentoo-user@××××××××.net wrote:
> On Mon, 4 Feb 2002, Einar Karttunen wrote:
>
> > Hello
> >
> > I have thought about a new way of categorise ebuilds in gentoo. The
> > new scheme would be based on category files which would be just a
> > list of dependencys as portage understands them. Each package could
> > be in many categories and categories may include categories (but there
> > may be no circular references).
> >
>
> I agree on your point that category files are usefull. You certainly have
> a point. I don't think though the categories in the portage tree should
> vanish. I prefer to see category files as an addition to the "main
> category" of each package. The reason I want that is that I think the
> system would become unmanageable if the packages are uncategorized. There
> are just too many packages, if you want to put them all in one directory,
> it will be hell to find them or maintain them. Next the categorizing
> allows for duplicate names. Finally I think category files with qualified
> packages are not harder to make than category files without qualified
> packages. Unqualifying packages is a considerable job though, so I prefer
> to give each package a "main" category, and use category files for
> aditional categories.
Just an idea:
to simplify it we can have *optional* KEYWORDS="xxx yyy" in 
ebuild file, and "emerge --update-keywords" command to
scan through available ebuilds and dump their names to apropriate files
under /usr/portage/keywords
i.e. if in dev-lang/python-2.1.1-r3.ebuild, there's 
KEYWORD="DEVELOPMENT PYTHON COMPILER"  
dev-lang/python-2.1.1-r3 will be appended to 
/usr/portage/keywords/{DEVELOPMENT,PYTHON,COMPILER}

	/Vitaly