| 1 |
On Tue, 11 Sep 2007 03:36:13 +0200 |
| 2 |
Volker Armin Hemmann <volker.armin.hemmann@××××××××××××.de> wrote: |
| 3 |
|
| 4 |
> On Dienstag, 11. September 2007, Roy Wright wrote: |
| 5 |
> > Howdy, |
| 6 |
> > |
| 7 |
> > Well, I had to local mask |
| 8 |
> > |
| 9 |
> > =x11-base/xorg-server-1.4-r1 |
| 10 |
> > =x11-base/xorg-server-1.4 |
| 11 |
> > =x11-base/xorg-x11-7.3 |
| 12 |
> > |
| 13 |
> > today to keep portage from blocking. My guess |
| 14 |
> > is that eventually a new version of nvidia-drivers |
| 15 |
> > will be available and a new revision of xorg-server |
| 16 |
> > will arrive that will support it (no longer block all |
| 17 |
> > versions of nvidia-drivers). |
| 18 |
> > |
| 19 |
> > Until that time will probably just keep masking |
| 20 |
> > xorg-server and hope I remember to unmask |
| 21 |
> > xorg-x11 at that time. |
| 22 |
> > |
| 23 |
> > This seems inelegant. So I'm hoping someone |
| 24 |
> > has a better approach. |
| 25 |
|
| 26 |
The really inelegant solution would be not to have the blocker. |
| 27 |
Most people would just update without looking even at the |
| 28 |
emerge -puDvN world output, and them complain on a huge and |
| 29 |
useless thread on the forums, because something broke :P |
| 30 |
|
| 31 |
If you have the blocker, you can't screw up the thing. Blockers |
| 32 |
are the only solution for incompatible packages, and the new xorg |
| 33 |
version is incompatible with all the nvidia-drivers version. In |
| 34 |
fact, no future version of xorg will fix this, since it is completely |
| 35 |
nvidia-side. So, I would change your snipped above by this one: |
| 36 |
|
| 37 |
>=x11-base/xorg-server-1.4-r1 |
| 38 |
>=x11-base/xorg-server-1.4 |
| 39 |
>=x11-base/xorg-x11-7.3 |
| 40 |
|
| 41 |
Note, the '>=' in front of the packages, those are not quotations |
| 42 |
starting with '>', but '>=', because any new version will have the |
| 43 |
same problem (since as I said, the problem is in the drivers, that |
| 44 |
are just outdated). |
| 45 |
|
| 46 |
If you have to incompatible packages, you need to decide what |
| 47 |
your priority is, period. There is no way around that, until |
| 48 |
nvidia decides to release a new version that is compatible with |
| 49 |
the new abi. |
| 50 |
|
| 51 |
|
| 52 |
> remove the blocker? the current nvidia-drivers work fine, if you |
| 53 |
> add -ignoreAbi to your X-start script (like kdm conf). |
| 54 |
|
| 55 |
So the nvidia people say. Though I can confirm that in my installation |
| 56 |
it doesn't work. It just lockups (and yes, I am sure that X composite |
| 57 |
was off, because I always have it off). |
| 58 |
|
| 59 |
-- |
| 60 |
Jesús Guerrero <i92guboj@×××××.es> |
| 61 |
-- |
| 62 |
gentoo-user@g.o mailing list |
Archives