severity 679228 normal
thanks
Hi,
Le 27/06/2012 12:16, Ansgar Burchardt a écrit :
> Package: ocl-icd-libopencl1
> Version: 1.1-1
> Severity: serious
>
> ocl-icd-libopencl1 ships the unversioned .so in the library runtime
> package, however Policy 8.2 says
>
> ----
> If your package contains files whose names do not change with each
> change in the library shared object version, you must not put them in
> the shared library package. Otherwise, several versions of the shared
> library cannot be installed at the same time without filename clashes,
> making upgrades and transitions unnecessarily difficult.
> ----
Our libopencl1 shared library has a proper SONAME (libopencl.so.1).
Note that, as this is a free implementation of a library implemented
by several vendors, we *need* to keep in sync with them if we want
to keep binary compatibility. I plan to diffuse on d-d a document
about the situation of OpenCL in Debian. I will try to think to cc
this bug.
In this case, the .so symlink is kept in the library package (instead
of putting it in the dev package) because Intel version of the library
use the "libopencl.so" soname instead of "libopencl.so.1".
We plan to solve this issue with Intel in order to keep binary
compatibility but this is not done yet.
Note that amd-libopencl1 and nvidia-libopencl1 packages do the
same thing.
> It looks like this was fixed, but then reverted again as the changelog
> for 1.3-2 says
>
> ----
> * in particular, move the .so from -dev to -libopencl1 in order
> to support programs created with the Intel SDK
> ----
Yes, we want to keep the binary compatibility with respect to OpenCL
compiled with the Intel SDK.
When and if a new libOpenCL library appears, then Intel would be
required to also use soname (even if we do not succeed into changing
Intel behavior before).
At this time, it will be easy to release a version of this package
without the so link (and put it in the -dev package).
Note that, at that time, the conflict/replace will be between the
current package and the new -dev package.
Current package (or update of current package) and new shared lib
package will be co-installable.
And update of current package, new shared lib package and new -dev
package will be co-installable.
=> for all these reasons, I downgraded the severity to "normal"
So, until Intel shared library in it's SDK is fixed *or* that a
new version (soname) of libOpenCL is release/requested by the
Khronos group (the one that normalize OpenCL), I will let the .so
symlink in this library package.
Regards,
Vincent
> Regards,
> Ansgar
--
Vincent Danjean GPG key ID 0x9D025E87 vdanj...@debian.org
GPG key fingerprint: FC95 08A6 854D DB48 4B9A 8A94 0BF7 7867 9D02 5E87
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
