1 |
>>>>> On Sat, 11 Apr 2020, Marek Szuba wrote: |
2 |
|
3 |
> Title: Manual steps required during upgrade to an eselect-free OpenCL set-up |
4 |
|
5 |
Title is too long. |
6 |
|
7 |
> Author: Marek Szuba <marecki@g.o> |
8 |
> Posted: 2020-05-01 |
9 |
> Revision: 1 |
10 |
> News-Item-Format: 2.0 |
11 |
> Display-If-Installed: app-eselect/eselect-opencl |
12 |
|
13 |
> We are now in the process of migrating OpenCL in Gentoo to having all |
14 |
|
15 |
Maybe avoid first person? |
16 |
|
17 |
> implementations operate through an ICD loader (dev-libs/ocl-icd or |
18 |
> dev-libs/opencl-icd-loader) installed directly into /usr instead of |
19 |
> using eselect-opencl to switch between implementations. eselect-free |
20 |
> versions |
21 |
|
22 |
"eselect-free versions" is a strange term. Also, why a line break after |
23 |
"versions"? |
24 |
|
25 |
> of loader packages have just been released to the public. |
26 |
|
27 |
> Unfortunately although the upgrade to those versions will automatically |
28 |
> uninstall app-eselect/eselect-opencl, it will not remove the symbolic |
29 |
> links to |
30 |
|
31 |
Another funny line break. |
32 |
|
33 |
> libOpenCL.so created by this tool in library directories because those links |
34 |
> are not owned by the package in question. If your system is configured for |
35 |
> full collision protection (FEATURES=collision-protect), it will be necessary |
36 |
> to manually remove those links |
37 |
|
38 |
> rm -i /usr/lib{,64}/libOpenCL.so* |
39 |
|
40 |
> before running the upgrade. |
41 |
|
42 |
Can't this be done automatically, e.g., in pkg_preinst of the replacing |
43 |
package? |
44 |
|
45 |
> Systems whose collision protection either allows overwriting orphaned files |
46 |
> (FEATURES='-collision-protect protect-owned') or which do not use collision |
47 |
> protection at all (not recommended) should be unaffected. |