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

RPM Fusion Bugzilla noreply at rpmfusion.org
Sat Feb 21 19:59:09 CET 2009


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





--- Comment #44 from Thorsten Leemhuis <fedora at leemhuis.info>  2009-02-21 19:59:08 ---
(In reply to comment #43)
> (In reply to comment #40)
> > ping -- how to get things rolling? kwizart, could you maybe review this? I have
> > no systems with nvidia or ati hardware at hand to test this, so I don#t feel
> > comfortable to review this
> Actually, it would be great if you could test it (even if you don't review)
> since I'm in the opposite situation - I only have ATI/nVidia cards and no Intel
> or other integrated GPUs. I think the non-ati-nvidia case should be handled,
> but just to make sure...

What do you want see tested on intel hardware?

But whatever:  I guess the tool should just say something like "this tool only
manages proprietary nonfree drivers; there are no such drivers for your
hardware so you won't need this tool" or something like that

> (In reply to comment #42)
> > one more comment: why is stuff stored in /etc/rpmfusion-config-display.d ? I'd
> > say users should never modify those files (or should they?), so /usr/share
> > might be the better place
> Hm.... Good point. I wanted to make the design work with 3rd parties though, so
> anybody could drop a file in /etc/rpmfusion-config-display.d and then use their
> driver configuration. That would still be true for /usr/share, but /etc seems
> like a more appropriate spot for this (ie, like /etc/yum.repos.d or /etc/mock)

I'd say: definitely go for /usr/share then. Make it use
/etc/rpmfusion-config-display.d as second source if really needed, but I see no
reason for that. IOW: don#t create config files or files in /etc without strong
need


-- 
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.
You are the assignee for the bug.


More information about the rpmfusion-developers mailing list