Re: [gentoo-dev] Portage Subcategory Capabilities?

[Georgi Georgiev]

maillog: 04/10/2004-00:16:10(-0700): George Shapovalov types
<snip>
> As for distinguishing: in prior discussions there were calls to go the
> opposite route and flatten namespace. That is to get rid of categories
> altogether and rely solely on search. Thus one approach would be to make one
> pass accumulating all package names and then work off that (store path to
> ebuild dir in the cache for example). However that may not be optimal as this
> will disallow duplicate package names (which we *have* irrespectively of
> whether this is good or bad).

I remember that discussion. And there were to be symlinks to the
packages in the flat namespace, similar to what we already have in
$PKGDIR.

<snip>
> A simpler and more efficient approach may be to simply prepend path to package
> name, possibly substituting '/' with some other separator if that's a
> problem. This will give a flat list of effective package names (that include
> all their categorization) which may even simplify further processing.
> Actually having a separate pass may be even more of an advantage as portage
> works off its cache for the most part anyway and this cache is created
> server-side already. Thus this change might even speed things up :) (well,
> not really, but shouldn't cause significant performance degradation either).

Naah, that would also require users to specify full names, which is
ugly.

<snip>
> > 3) the many additional directories would cause an 'emerge sync' to take
> >     longer than it does now.

Having 100 or so more directories when there are 80,000+ items in $PORTDIR
wouldn't really hurt rsync.

-- 
*>   Georgi Georgiev   *> If you go out of your mind, do it quietly,   *>
<*    chutz@×××.net    <* so as not to disturb those around you.       <*
*>  [phone]   *>                                              *>

--
gentoo-dev@g.o mailing list