[Pkg-opencl-devel] Bug#823528: llvmopencl.so.5 should be packaged in it's own binary package

[Matthias Klose]

On 07.05.2016 10:03, Vincent Danjean wrote:
> Le 05/05/2016 20:04, Matthias Klose a écrit :
>> Package: src:pocl
>> Version: 0.13-1
>>
>> Found while looking at packaging 0.13 to be able to use llvm-3.8.
>> libpocl1 ships another library llvmopencl.so.5 in the package.
>> In 0.13, the llvmopencl soname is bumped to 7, which the libpocl
>> soname stays at 1.  So you have to rename libpocl1 to e.g.
>> libpocl1-7 in any case, however why not packaging this library as
>> a separate binary?
>
> llvmopencl.so.5 is a private library ship in $libdir/pocl/ and not
> $libdir. Nothing but binaries from the pocl package itself must link
> to it (and, if I recall correctly, only the libpocl library itself
> link to it). So, I'm not convinced to the need of another library
> Debian package.
>    Being in the same binary package ensure they upgrade at the same
> time and avoid to have to ensure the same things with dependencies.
> Upstream really managed them together and do not support using
> different version. Supporting it in Debian can be done (with more
> manpower) but I do not see any benefice.
>    Do not hesitate to present other arguments as, for now, I'm really
> not convinced that "llvmopencl.so.5 should be packaged in it's own
> binary package"

thanks for clarifying.  However I also saw dropped symbols in the libpocl.so.1 
library, so it looks like the library packages needs to be renamed for 0.13.