1 |
On 2020-04-11 14:54, Brian Evans wrote: |
2 |
|
3 |
> I would mention that FEATURES='-collision-protect protect-owned' is |
4 |
> the default so most people won't have any action to take at all. |
5 |
|
6 |
I've been wondering what the default is these days. Good point, in fact |
7 |
I'll swap the case around so that the flow of the news item is "with |
8 |
default configuration nothing will happen, if however you have strict |
9 |
collision check do this". |
10 |
|
11 |
|
12 |
|
13 |
On 2020-04-11 17:04, Ulrich Mueller wrote: |
14 |
|
15 |
>> Title: Manual steps required during upgrade to an eselect-free |
16 |
>> OpenCL set-up |
17 |
> |
18 |
> Title is too long. |
19 |
|
20 |
OK, I'll shorten it. |
21 |
|
22 |
>> We are now in the process of migrating OpenCL in Gentoo to having |
23 |
>> all |
24 |
> |
25 |
> Maybe avoid first person? |
26 |
|
27 |
Can do. |
28 |
|
29 |
> "eselect-free versions" is a strange term. |
30 |
|
31 |
How about simply "updated versions"? |
32 |
|
33 |
> Also, why a line break after "versions"? |
34 |
|
35 |
It's just because Thunderbird breaks lines at fewer characters than Vim |
36 |
in text-file mode. It isn't present in the actual news item. |
37 |
|
38 |
> Another funny line break. |
39 |
|
40 |
Again, Thunderbird's fault. |
41 |
|
42 |
>> libOpenCL.so created by this tool in library directories because |
43 |
>> those links are not owned by the package in question. If your |
44 |
>> system is configured for full collision protection |
45 |
>> (FEATURES=collision-protect), it will be necessary to manually |
46 |
>> remove those links |
47 |
> |
48 |
>> rm -i /usr/lib{,64}/libOpenCL.so* |
49 |
> |
50 |
>> before running the upgrade. |
51 |
> |
52 |
> Can't this be done automatically, e.g., in pkg_preinst of the |
53 |
> replacing package? |
54 |
|
55 |
I have tried doing this in pkg_preinst but alas, I have found out |
56 |
collision checks are performed before that function is invoked. I have |
57 |
also tried setting COLLISION_IGNORE in the replacing package but it |
58 |
seems that variable only works in make.conf and make.defaults - in which |
59 |
case it's simpler to simply tell the users to delete those symlinks. |
60 |
|
61 |
-- |
62 |
MS |