I posted a message to him on the aur page for opencl-headers.

And I did fix the problem on my computer, but for users who try to install my package they wont be able to do so unless they manually fix opencl-headers themselves.

So any suggestions on how to fix this?

I can see a couple of possible fixes:

a) opencl-headers simply conflicts=(nvidia-utils) and then people install it with -f

Sorry typo. I meant to say: a) opencl-headers removes "conflicts=('nvidia-utils')" and then people install it with -f ... and it appears that this is what the author has decided to do, he just replied that he will remove the conflicts. -- Best regards, Alex Combas

On 09/09/10 09:26, Alex Combas wrote:

On Wed, Sep 8, 2010 at 1:32 PM, Nathan O wrote:

...

First thing I would do, is to contact the maintainer of the package, and temporarily edit the PKGBUILD of the package that is giving you the problem if you are wanting to install it.

I posted a message to him on the aur page for opencl-headers.

And I did fix the problem on my computer, but for users who try to install my package they wont be able to do so unless they manually fix opencl-headers themselves.

So any suggestions on how to fix this?

I can see a couple of possible fixes:

a) opencl-headers simply conflicts=(nvidia-utils) and then people install it with -f

b) opencl-headers removes cl.h cl_gl.h and cl_platform.h since they are provided by nvidia-utils

c) nvidia-utils removes cl.h cl_gl.h and cl_platform.h since they are provided by opencl-headers

d) ???

Any other suggestions?

Just wait for the next driver release, which removes these headers: http://www.nvnews.net/vbulletin/showthread.php?p=2314331 (unless of course they are put in the Arch package anyway) Jonathan

On Thu, 2010-09-09 at 09:53 +0200, Lukáš Jirkovský wrote:

On 8 September 2010 22:00, Alex Combas wrote:

...

What is the best way to resolve conflicting files in aur packages?

I've run into this issue a couple times recently, first of all with "panda3d-cvs" and "cuda-toolkit" both contained the file /usr/bin/bin2c

The result was the panda3d-cvs maintainer just removed the file since he said it wasn't doing anything anyway.

Now I've run into a similar problem but this time the maintainer fixed it a different way and it broke my package.

opencl-headers http://aur.archlinux.org/packages.php?ID=35367 has 3 files which are also provided by nvidia-utils

So now to fix it the maintainer of opencl-headers has added conflicts=(nvidia-utils) to his package.

But my problem is that I recently made a package (luxrays-hg) which depends=('nvidia-utils') and also makedepends=('opencl-headers')

So my package (luxrays-hg) will no longer install because 2 of its decencies (opencl-headers & nvidia-utils) are in conflict.

So what is the best practice in this situation?

-- Best regards, Alex Combas goplexian.com

Hello Alex, as Jonathan said the best thing would be to wait for a new driver release with openCL headers removed.

By the way I tried to use the headers supplied with nvidia-utils but compilation fails with them. I was able to build luxrays-hg with forcing opencl-headers to install (headers from nvidia-utils are overwritten then). Maybe you can post a note to the package comments that the users should force the installation of opencl-headers until there is a new nvidia-utils in the repo.

Nvidia's beta release has shifted some headers (not sure if they're these specific ones) out of the driver.