-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Georgi Georgiev wrote: | maillog: 10/08/2005-23:01:30(-0700): Donnie Berkholz types |>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.
OK, so one of them does. And I still consider that broken behavior. |>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. There are a couple of reasons this isn't very interesting to me. 1) It involves work on the monolithic package, which I'd rather not spend any more time on. 2) Keeping all changes in one big chunk makes for an easier transition than spreading them out, because users only have to figure things out once. So sticking it in with the modular move makes sense to me. Thanks, Donnie -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC+vhmXVaO67S1rtsRAvv9AKDqeISd638V/UXDby4l9jkue/tN/ACgs2oY gCQwlInZ2m7zfOQfcovvZxk= =FKsB -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list
