--- Comment #28 from Thorsten Leemhuis <fedora(a)leemhuis.info> 2009-01-07 19:38:28
(In reply to comment #23)
(In reply to comment #21)
> No; it IMHO definitely should be part of the driver package and completely auto
> generated there. Maintaining such a package manually sounds way to complicated
> to me -- especially when it comes to people that mix packages from updates,
> updates-testing or other repos (rawhide, external)
The config files can't be autogenerated, as they'll change from release to
release (for example, the past 2 versions of fglrx require a Screen section
while the previous releases didn't) and they include the PCI IDs of the
supported hardware as well... I mean, either way something has manual, but with
this setup we'll be changing an option in the config file instead of changing
the initscripts or foo-config-display scripts all the time.
Well, I mainly meant the list with the PCI IDs should get auto-generated. But
whatever: the data afaics definitely needs to be in a driver subpackage that
has a hard, versioned dep on the main driver package. Otherwise crazy things
might happen if (for example) a users updates to a update-testing driver (and a
geneeric rpmfusion-gpu-hwinfo package from testing( and later downgrades to the
older driver from stable (which would need the older rpmfusion-gpu-hwinfo).
(In reply to comment #24)
I worked on rpmfusion-config-display for many hours today, here's
stand at the moment:
- Added support for autoselection of the correct driver when multiple GPUs are
- Users are notified when none of the drivers support their hardware
- Profile script checks for running X server before outputting a warning
- RPM checks to test driver installation are functional
Sounds good. Thx for your work!
I also experimented with the dynamic radio buttons,
As mentioned earlier already: if that a lot of work just ignore it and go for a
solution that is easier to implement as easy to use (like the one in your
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.