[Pkg-fglrx-devel] Using alternatives instead of a conflict for libopencl1?

Simon Richter sjr at debian.org
Mon Apr 22 10:41:23 UTC 2013


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I've just introduced "Beignet", which is Intel's Open Source OpenCL
implementation for Ivy Bridge, into Debian. The library can be loaded
either as a full OpenCL implementation or as an ICD driver, so I'd
like to avoid two separate packages for both modes, which leaves the
problem that I need to introduce a Conflicts: if I use the
libOpenCL.so.1 name.

Would it make sense in your opinion to have libOpenCL.so.1 managed via
the alternatives subsystem instead?

I'd give the highest priority to the ICD loader, and give the vendor
specific implementations the same lower level.

   Simon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iJwEAQECAAYFAlF1E9IACgkQ0sfeulffv7ud/wP/flARx63rP8kaJos5rPv44mj1
yqfdRtwp/G4s7sk5XVdcthzh06Tb6vCpOwLBcYyWkQXl95WL5n/cO5YwNftSBoc1
jy/pO6sY04lP+qFZarw0iyXjG4wyJD2TcROerFUaNQ174Z6y/hxGjVkxea1W9Qi2
aiHTA4aDNNFBFT6Njnw=
=0QIB
-----END PGP SIGNATURE-----



More information about the Pkg-fglrx-devel mailing list