The conflict with nvidia-opencl-dev isn't so much of a problem - the two packages are both implementations of the OpenCL loader, right? So while it could be nice to be able to have both installed and use alternatives to select one, it's not really necessary. You can use one implementation of the OpenCL loader to load a different implementor's OpenCL ICD.
The more serious problem is that you have to work around the libopencl1 conflict between ocl-icd-libopencl1 and nvidia-304 (i.e. nvidia-current). In order to get hardware-acceleration I need nvidia-304; to get an OpenCL-1.2 compatible loader I need ocl-icd-libopencl1, and so I have to install the latter with --force-conflicts.
The conflict with nvidia-opencl-dev isn't so much of a problem - the two packages are both implementations of the OpenCL loader, right? So while it could be nice to be able to have both installed and use alternatives to select one, it's not really necessary. You can use one implementation of the OpenCL loader to load a different implementor's OpenCL ICD.
The more serious problem is that you have to work around the libopencl1 conflict between ocl-icd-libopencl1 and nvidia-304 (i.e. nvidia-current). In order to get hardware- acceleration I need nvidia-304; to get an OpenCL-1.2 compatible loader I need ocl-icd-libopencl1, and so I have to install the latter with --force-conflicts.