On Thu, Oct 03, 2013 at 01:04:09PM +0200, David Kalnischkies wrote:
On Thu, Oct 3, 2013 at 11:54 AM, Vincent Danjean vdanjean...@free.fr wrote:
I tried several variation, adding :same and/or :i386/:amd64 to
the Conflicts and/or Provides in ICD Loader. I do not succeed into
:same doesn't
Le 03/10/2013 13:28, Simon McVittie a écrit :
On 03/10/13 10:54, Vincent Danjean wrote:
The only problem is that it is not currently possible to install
an ICD Loader:i386 from one vendor and an ICD Loader:amd64 from another
vendor.
Is there a valid reason to do that, other than because I
Le 03/10/2013 13:04, David Kalnischkies a écrit :
On Thu, Oct 3, 2013 at 11:54 AM, Vincent Danjean vdanjean...@free.fr wrote:
I tried several variation, adding :same and/or :i386/:amd64 to
the Conflicts and/or Provides in ICD Loader. I do not succeed into
:same doesn't exist (in this
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
Hi,
While trying to setup a correct description of dependencies for OpenCL
eco-system, we got a problem related to multi-arch. I will try to describe
here a simplified version of the situation to illustrate our main problem
(ie I do not take into account the various versions of OpenCL that
On Thu, Oct 3, 2013 at 11:54 AM, Vincent Danjean vdanjean...@free.fr wrote:
I tried several variation, adding :same and/or :i386/:amd64 to
the Conflicts and/or Provides in ICD Loader. I do not succeed into
:same doesn't exist (in this context), where did you find that?
Anyway, negative
On 03/10/13 10:54, Vincent Danjean wrote:
The only problem is that it is not currently possible to install
an ICD Loader:i386 from one vendor and an ICD Loader:amd64 from another
vendor.
Is there a valid reason to do that, other than because I can? If
nobody would actually want to do that,
7 matches
Mail list logo
