On Tue, Sep 20, 2005 at 10:01:39AM +0300, Alin Nastac wrote: > Georgi Georgiev wrote: > >maillog: 20/09/2005-09:37:23(+0300): Alin Nastac types > >>Georgi Georgiev wrote: > >>>- that package in my overlay that has net-wireless/gnome-phone-manager > >>> in its *DEPENDs to work for as long as needed > >>> > >>gnome-phone-manager can be found in portage tree under app-mobilephone > >>category. > > > >So that's why my overlay got screwed up! > > > >But seriously, this only supports my point -- category moves are evil.
> portage isn't supposed to offer eternal functionality status for > personal overlays. Eh? > what if an eclass gets obsoleted and eventually is > removed from the tree? Pull from viewcvs. I assume you're talking about portage >=2.1 capabilities, since you *cannot* remove an eclass from the tree once it's been added currently. > the only problem is binary packages screw up. Binpkgs should be running from their own env, they should be stand alone not requiring even a tree. Back on subject... I *really* don't like categories. Single vdb, single repo, single binpkg, it's not horrible. Multiple true, standalone repos, with the occasional binpkg repo used? It makes doing the category move *really* rather hard, since you need to track down exactly which repository and ebuild came from. ~harring
pgp81JlK7zAMI.pgp
Description: PGP signature
