On Thu, Oct 03, 2013 at 11:54:55AM +0200, Vincent Danjean wrote: > > The current proposal about Depends/Conflicts/Provides is the following: > ICD Loader: > =========== > Section: libs > Multi-Arch: same > Architecture: any > Provides: libopencl1 > Conflicts: libopencl1 > Replaces: libopencl1 > Suggests (or Recommends): opencl-icd
That Replaces makes no sense. Why isn't that a Depends on opencl-icd? I assume a loader is useless without any implementations being installed, and the application would just depend on libopencl1 instead of both virtual packages. Or is there a fallback mechanism so that OpenCL applications can work without one? But then I have to wonder how someone would install things that want to use OpenCL. I just want to install the application and it should hopefully install the opencl implementation for the hardware I want to use, possible all available ones. And I think the only way to do something like that is to have a package depend on all the implementations. And you could perhaps than just Recommend that package. Kurt -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131004230622.ga9...@roeckx.be
