On Wednesday 04 June 2003 16:23, Rolf Veen wrote: > George Shapovalov wrote: > > Ok, this seems to be pretty much it, at least from what I remember > > being mentioned on this topic. Again, if anybody thinks I ommitted > > something, please stand up and mention it :). > > Namespace orthogonal to categories. > > Categories change, as packages are being added; if a category has more > that N (lets say 50, for example) entries it looses its usefullness. > While browsing for packages it is natural to have some level of depth; > two or tree levels of categories should be ok. Also a package can fit > into more that one category. Let categories be a graph. A symlink > hierarchy, for example. Unfortunately CVS does not work well with symlinks, so this is not really an option. Also there is an advantage in being able to have one unique name for a package. > > But since categories are variable and somewhat arbitrary, don't let > the basic system, the core algorithms, depend on them. So take a flat > namespace for packages, resolving name conficts in the download (url > to local dir) phase, adding the necesary information to the ebuild. We need unique names. For me category/name is a good way, and certainly better than UID's (Like microsoft uses) as those are impossible to remember and easy to do wrong. Also we have a central repository, so we don't need to worry about clashes that much. > > Concluding, have a flat namespace for machine interaction, and an > arbitrarily complicated category graph on top of that for user > interaction. Flat namespaces are actually slower in machine interaction. There are allready very many packages in portage currently. Thousands of entries in a directory is NOT fun to look at, or to search for a computer (albeight doable). My suggestion would be an alias list simmilar to the virtuals list, but one that is not allowed inside ebuilds. In those ways packages can still be presented in multiple categories, while the aliasses do not interfere with the inner workings of portage. Paul -- Paul de Vrieze Researcher Mail: pauldv@cs.kun.nl Homepage: http://www.devrieze.net