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