>>>>> On Sat, 11 Apr 2020, Marek Szuba wrote: > Title: Manual steps required during upgrade to an eselect-free OpenCL set-up
Title is too long.
> Author: Marek Szuba <mare...@gentoo.org>
> Posted: 2020-05-01
> Revision: 1
> News-Item-Format: 2.0
> Display-If-Installed: app-eselect/eselect-opencl
> We are now in the process of migrating OpenCL in Gentoo to having all
Maybe avoid first person?
> implementations operate through an ICD loader (dev-libs/ocl-icd or
> dev-libs/opencl-icd-loader) installed directly into /usr instead of
> using eselect-opencl to switch between implementations. eselect-free
> versions
"eselect-free versions" is a strange term. Also, why a line break after
"versions"?
> of loader packages have just been released to the public.
> Unfortunately although the upgrade to those versions will automatically
> uninstall app-eselect/eselect-opencl, it will not remove the symbolic
> links to
Another funny line break.
> libOpenCL.so created by this tool in library directories because those links
> are not owned by the package in question. If your system is configured for
> full collision protection (FEATURES=collision-protect), it will be necessary
> to manually remove those links
> rm -i /usr/lib{,64}/libOpenCL.so*
> before running the upgrade.
Can't this be done automatically, e.g., in pkg_preinst of the replacing
package?
> Systems whose collision protection either allows overwriting orphaned files
> (FEATURES='-collision-protect protect-owned') or which do not use collision
> protection at all (not recommended) should be unaffected.
signature.asc
Description: PGP signature
