more virtual packages for providing libcuda.so.1 and libOpenCL.so.1
Alberto Milone
alberto.milone at canonical.com
Thu Jul 4 15:07:45 UTC 2013
On 04/07/13 17:01, Andreas Beckmann wrote:
> How does Ubuntu handle the (non-)coinstallability of nvidia-current,
> nvidia-304, nvidia-310, ...?
>
nvidia-current and nvidia-current-updates are simply transitional
packages for nvidia-304 and nvidia-304, at least in Ubuntu 13.10. It is
no longer possible to install more than one nvidia driver at the same
time (they all conflict/replace/provide the same virtual package).
> For CUDA, you should have a
> Provides: libcuda-5.0-1
> in those packages, but probably no Conflicts/Breaks/Replaces.
>
> And soon you need to provide additionally
> Provides: libcuda-5.5-1
>
> This is because there are no versioned Provides.
>
>
> nvidia-cuda-toolkit will get
> Build-Depends: libcuda1 (>= 3XX) | libcuda-5.0-1
> and the current beta will get
> Build-Depends: libcuda1 (>= 3YY) | libcuda-5.5-1
> (and the Depends in libcudart* will be similar).
>
Good point.
>
> For OpenCL it depends on whether we need to distinguish versions.
> If we can go with only one version for now, I would suggest to use the
> already existing libopencl1 virtual package.
>
> If we need specifically 1.2 or later, use libopencl-1.2-1 as the virtual
> package name.
>
It sounds good to me.
--
Alberto Milone
Software Engineer
Hardware Enablement Team
Professional and Engineering Services
More information about the pkg-nvidia-devel
mailing list