An eselect module to manage /etc//X11/xorg.conf symlink. http://code.google.com/p/krigstasks-samling/downloads/list Reproducible: Always
Created attachment 225217 [details] eselect-xorgconf-0.1.ebuild eselect-xorgconf-0.1.ebuild
Created attachment 225219 [details] metadata.xml metadata.xml
What is it good for? I mean to eselect xorg.confs?
(In reply to comment #3) > What is it good for? > I mean to eselect xorg.confs? No idea either :-) X now starts without any xorg.conf for most people. If you can get this working w/ xorg.conf.d directory structure for the upcoming xorg-server 1.8 w/ udev support [1], then it might eventually be of some use. [1] http://who-t.blogspot.com/2010/01/new-configuration-world-order.html
Hello guys, I'm the author (for the lack of better word) of this module. I use this tool to switch between nvidia config with TwinView and Xrandr-based nouveau one (see provided URL). gtlinuxman might say what does he use it for too. As for (In reply to comment #4) > If you can get this working w/ xorg.conf.d directory structure for the upcoming > xorg-server 1.8 w/ udev support [1], then it might eventually be of some use. I think I will support this too, it doesn't seem very hard (though it'll require two modules, I think). But I'll wait for Xorg 1.8 in ~amd64 to implement and test it. Thanks for link about 1.8, by the way.
(In reply to comment #5) > I think I will support this too, it doesn't seem very hard (though it'll > require two modules, I think). But I'll wait for Xorg 1.8 in ~amd64 to > implement and test it. Thanks for link about 1.8, by the way. Well, I imagine that more or less shameless copy of eselect-fontconfig should do the job there, assuming you can work the config files layout out w/ x11 folks. For the former cited use case, very much an overkill.
@gtlinuxman Please do not change the status of a bug to assigned. It isn't assigned as long no gentoo dev took it.
Future xorg-server supports directory xorg.conf.d/ where it can be separated into more files. How would your eselect tool handle that?
I did not really think of it, to be honest, so I would like to ask for advice. I think that most appropriate thing to do is to implement two modules: the first is current module for symlinking main config, and the other , eselect-xorgd or something, working like eselect-fontconfig, enabling/disabling portions in /etc/X11/xorg.d/ (In reply to comment #8) > Future xorg-server supports directory > xorg.conf.d/ > where it can be separated into more files. > > How would your eselect tool handle that?
I need your advice, guys. I did (as Doktor Notor suggsted) mercilessly hack eselect-fontconfig and came up with this draft: http://code.google.com/p/krigstasks-samling/source/browse/xorg.conf.d.eselect?repo=esel-xconf (yep, still there's room for polishing at least) As it is, module does take care of symlinking files from /etc/X11/xorg.conf.avail to /etc/X11/xorg.conf.d So I want some advice from x11 herd andother competent people: should it use other directory for available config pieces? Should it support multiple directories maybe (like fontconfig does)? Some Xorg modules (x11-drivers/xf86-input-wacom, for example, as I was informed) install config piece in /usr/share, should we handle that too? Xorg comes with /etc/X11/xorg.conf.d/10-evdev.conf already in place, so for it to be eselectable user should manually move it to xorg.conf.avail, that's not probably very good too, how could I workaround it? All the critics and suggestions for improvement are heartly welcome. By the way, app-admin/eselect-xorgconf-0.2 (still supporting monolythic configs only) is in rion overlay now.
Version 0.3 released, with support for modular configs.
Is there still any interest in adding this to the tree?
(In reply to Matt Turner from comment #12) > Is there still any interest in adding this to the tree? Seems like there's no much interest, so let it reside in rion-overlay, where I can kind-of-support it on my own :)
