On 02/09/2014 16:43, Graham Inggs wrote:
> On 01/09/2014 17:00, Vincent Danjean wrote:
>> Here is what I put in the package I will upload this evening:
>>
>> Package: ocl-icd-opencl-dev
>> [...]
>> Conflicts: opencl-dev
>> Breaks: ocl-icd-libopencl1 (<< 2.1.3-5~), nvidia-libopencl1 (<<304.88-7~),
>> amd-libopencl1 (<<1:13.4-4~)
>> Replaces: opencl-dev, ocl-icd-libopencl1 (<< 2.1.3-5~), nvidia-libopencl1
>> (<<304.88-7~), amd-libopencl1 (<<1:13.4-4~)
>> [...]
>>
>> Version number are based on the data you provide into the bugreport
>> (thank you very much for this). nvidia-opencl-dev and
>> amd-opencl-dev probably needs both the same list of
>> Conflicts/Breaks/Replaces wrt. the libOpenCL.so symlink move.
>
> I'm pretty sure nvidia-opencl-dev and amd-opencl-dev will only need:
>
> Breaks: ocl-icd-libopencl1 (<< 2.1.3-5~)
> Replaces: ocl-icd-libopencl1 (<< 2.1.3-5~)
>
> ...as they already conflict on each other because of the opencl-dev
> virtual package, and conflicts is a stronger relationship than
> breaks/replaces.
Yes for -dev packages. But what if a user with nvidia-libopencl1/stable
installed (ie *not* the -dev package) tries to install
amd-opencl-dev/testing ?
Are you sure that nvidia-libopencl1 will be removed (not just
unconfigurated) before amd-opencl-dev is unpacked ?
Both nvidia-libopencl1/stable and amd-opencl-dev/testing contains
the .so symlink.
Regards,
Vincent
PS: note that policy 7.6.2 gives as example the mail-transport-agent
virtual package where Provides, Conflicts *and* Replaces are used.
--
Vincent Danjean GPG key ID 0xD17897FA vdanj...@debian.org
GPG key fingerprint: 621E 3509 654D D77C 43F5 CA4A F6AE F2AF D178 97FA
Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html
APT repo: deb http://people.debian.org/~vdanjean/debian unstable main
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
