| 1 |
yes I hit it too - back before it hit stable. It seemed that going xorg |
| 2 |
modular is a one way trip as you cant remove modular xorg easily unless |
| 3 |
you keep an independent record of every package installed. I was pissed |
| 4 |
because modular didnt work and I couldnt uninstall it! Eventually |
| 5 |
updates caught up with and fixed the problem, but in the meantime I had |
| 6 |
an unusable system. I realised the problem when I coulnt even downgrade |
| 7 |
from 7.1 to 7.0 - this loss of control is a major pita with modular X. |
| 8 |
|
| 9 |
BillK |
| 10 |
|
| 11 |
|
| 12 |
On Sun, 2006-07-02 at 13:24 -0700, Donnie Berkholz wrote: |
| 13 |
> Bo Ørsted Andresen wrote: |
| 14 |
> > When user upgrades to modular X.org there is a block that requires him to |
| 15 |
> > remove xorg-x11-6.8*. Then the user upgrades, reboots and finds out there is |
| 16 |
> > something wrong. So he downgrades. But when downgrading there is no block |
| 17 |
> > requiring him to remove modular X first. So he merges xorg-x11-6.8 which |
| 18 |
> > overwrites a *LOT* of modular X files like e.g. startx and only unmerges |
| 19 |
> > xorg-x11-7.0 which is a very small package. Now the user decides to upgrade |
| 20 |
> > again so he unmerges xorg-x11-6.8 again and it removes all the files but |
| 21 |
> > portage still thinks modular X is installed except of xorg-x11-7*. So when he |
| 22 |
> > emerges xorg-x11-7* that package is the only one which is remerged... |
| 23 |
> |
| 24 |
> That's a definite possibility. But I don't _think_ everyone encountering |
| 25 |
> this problem has hit it, although I could be wrong. |
| 26 |
> |
| 27 |
> Thanks, |
| 28 |
> Donnie |
| 29 |
> |
| 30 |
-- |
| 31 |
gentoo-user@g.o mailing list |
Archives