Re: [mongoose@users.sourceforge.net: X upgrade policy]
Quoting Christopher C. Chimelis (chris@debian.org):
> To end this long reply, I suggest this: compile your own Xserver and utah
> and install it in /usr/local until things work out to the point where they
> are usable again for your setup.
What I did was use the potato 3.3.6 xserver, because xserver-mach64
doesn't get built anymore, and repacked utah-glx without Conflicts:
xfree86-common(>=4.0) line.
For some more fun, today I built xserver-mach64 from 3.3.6-18 sources,
with very little problems - added it back to
debian/{control,create-arch-xservers} and to debian/patches/000a*
(whatever it's called). Now I have a xserver-mach64_3.3.6-18, almost
like it still existed in distro. ;-)
Had to do that because there is no DRI for mach64 yet, and I like
those nifty gl screensavers, not to mention tuxracer.
One could file a bug to utah-glx package and request replacing of
Conflicts: xfree86-common(>=4.0) with a dependency on
xserver-common-v3, or maybe on any of those xserver packages utah-glx
works with. That would deal with the removal of utah-glx on upgrade.
Zoran
--
menage a trois, n.:
Using both hands to masturbate.
Reply to: