maillog: 10/08/2005-23:01:30(-0700): Donnie Berkholz types > Georgi Georgiev wrote: > | Hm, why not just forget the transition, stick a warning telling people > | to add > | > | ModulesPath "/usr/lib/modules" > | ModulesPath "/usr/lib/xorg/modules" > > Needing to set ModulePath at all in a standard installation is broken. > This shouldn't need to be in a configuration file; none of the tools I'm > aware of generate files with ModulePath by default, and it really > doesn't make sense to. > > xorg.conf is difficult and user-unfriendly enough to set up already > without adding more Gentoo-only requirements to it.
Mmmm, xorgcfg does generate an xorg.conf with ModulePath in it. That's why I had it in mine in the first place. Anyway, I agree with your other points. maillog: 10/08/2005-22:08:36(-0700): Donnie Berkholz types > Georgi Georgiev wrote: > | What about new revisions of the monolithic xorg that will install in > | /usr/lib/xorg/modules followed by new revisions of all packages like > | opengl-update, nvidia, ati-whatever, that will depend on the newer xorg > | release? > > We still need to deal with the transition either way. We can't just > ignore everything that's installed in /usr/lib/modules when we upgrade xorg. I did not really understand the above. What I had in mind was making the transition now, rather than later. This would avoid the need for parallel ebuilds of all packages and if the appropriate packages block on appropriate revisions, it shouldn't cause much hassle. Unlike the /usr/X11R6 -> /usr move, there are only a few packages that install x modules (does anyone know how many packages these are?) so upgrading said packages shouldn't be much of a hassle. I never thought about ignoring /usr/lib/modules. -- -* Georgi Georgiev -* "Then you admit confirming not denying -* *- [EMAIL PROTECTED] *- you ever said that?" "NO! ... I mean Yes! *- -* +81(90)2877-8845 -* WHAT?" "I'll put `maybe.'" -- Bloom County -*
pgpUUcZ2drI5K.pgp
Description: PGP signature
