[Bug 171] Review Request: rpmfusion-config-display - tool to manage proprietary graphic drivers

RPM Fusion Bugzilla noreply at rpmfusion.org
Mon Feb 23 18:54:55 CET 2009


http://bugzilla.rpmfusion.org/show_bug.cgi?id=171


NicolasChauvet <kwizart at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED




--- Comment #49 from NicolasChauvet <kwizart at gmail.com>  2009-02-23 18:54:54 ---
Either we pick both /usr/share/rpmfusion-config-display/config and
/etc/rpmfusion-config-display.d to store the official configuration files.
Either just /etc/rpmfusion-config-display.d. But the files are aimed to be
customizeable by users, so it will eventually be better to keep only one
directory to avoid namespace issue with different directory rules.
Also it is important that only the files ending with .conf to be processed, so
backup files from edition (*~) will not be taken into account. Our own
"official" config files are meant to be set as %config and can get potentially
replaced at each update.

At this time, the tool in not ready for inclusion for few reasons:
- We need to froze the config FILES. (xvmc, avoid duplicate info, double
choices for modules)
- The tool need to be updated with the lastest scheme for replacement_xorg_libs
that could lead to avoid the needs of tweaking xorg.conf at all with F-10 and
beyond.
- We need to figure out about what to do with the vendor configuration tools
(multiple version shipped, only open sources ones for nvidia, allow to edit,
will they appear if the other vendor driver is activated).
- Tweaks for mesa-libGL removal for bogus application that want to dlopen
libGL.so.1 from the standard places.


Thoses are very the core functionality of the tool which are meant to be
available for thinking about the inclusion.


-- 
Configure bugmail: http://bugzilla.rpmfusion.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


More information about the rpmfusion-developers mailing list