[pkg-nvidia-devel] Anything waiting for upload?

[Russ Allbery]

Andreas Beckmann <debian at abeckmann.de> writes:

> Should we add a "Provides: nvidia-glx-whatever" to
> nvidia-glx{,-legacy-ABCxx} (the name of that virtual package still needs
> to be decided), so that addon packages could just "Suggests:
> nvidia-glx-whatever" instead of the full list of alternatives? Also
> fglrx-glx could just "Conflicts: nvidia-glx-whatever"

This is probably a good idea.  I think we should just use nvidia-glx as
the name of that thing to provide.  I believe that should work for the way
in which we're using it, and that will simplify how we handle all the
other dependencies.

We'll have to keep the full list of conflicts through a stable release,
though, or upgrades could break.

> Should we change nvidia-kernel-common from arch: all to arch: amd64
> i386? Even if it is buildable everywhere, it is only useful on platforms
> that actually have NVIDIA kernel modules.

Yes, that's probably a good idea.  It's a tiny package, so we're not
wasting much archive space and it avoids confusion.

> Same question goes for nvidia-xconfig (is it even still useful?) and
> nvclock (there is bug #551096) that are arch: any. But these packages
> you actually might use on other platforms that don't have NVIDIA driver
> support.

Yes, those should both list the specific NVIDIA-supported architectures
rather than being arch: any (and I'll request removal from the
architectures that are no longer supported).

-- 
Russ Allbery (rra at debian.org)               <http://www.eyrie.org/~eagle/>