NEW review of nvidia-settings-331

[Alberto Milone]

On 18/11/13 06:46, Martin Pitt wrote:
> Hey Alberto,
> 

Hi Martin

> nvidia-settings-311 has this in debian/control:
> 
> Package: nvidia-settings-319
> Architecture: i386 amd64
> Depends: nvidia-settings-331
> Description: Transitional package for nvidia-settings-310
>  This is a transitional package for nvidia-settings-310, and can be
>  safely removed after the installation is complete.
> 
> This at least needs some consistent versions. But are these -settings
> applications really that specific to particular driver versions?
> 
> If we just keep overwriting the old version with a new one with these
> transitional packages and Replaces/Conflicts/Provides, what's the
> purpose of having versioned package names in the first place? Could
> this not just be called "nvidia-settings"?
> 

I would very much like to keep only one nvidia-settings. The main
problem is that NVIDIA doesn't guarantee backward compatibility, however:
1) I could probably check the version and patch the code in case of problems
2) I haven't experienced any compatibility issues so far, except for one
with the legacy drivers (173)

So, I guess we could take our chances and go back to having just one
nvidia-settings for all the drivers.

> Also, into which component should this go, universe? I was hoping we
> could at some point drop the ancient python-gtk2 and
> screen-resolution-extra bits out of main.

nvidia-settings lives in main, as the drivers recommend it (which is
probably not a strict requirement).

as for screen-resolution-extra, at least the one in Trusty, it uses
python3-gi but it really shouldn't need any Gtk code, since we use the
package mainly to provide easy polkit access to nvidia-settings. I can
definitely remove the Gtk code from the package but let's leave it in
main (it will soon play a role in hybrid graphics).

Thanks,

-- 
Alberto Milone
Software Engineer
Hardware Enablement Team
Professional and Engineering Services