On 2020-04-11 14:54, Brian Evans wrote:

> I would mention that FEATURES='-collision-protect protect-owned' is 
> the default so most people won't have any action to take at all.

I've been wondering what the default is these days. Good point, in fact
I'll swap the case around so that the flow of the news item is "with
default configuration nothing will happen, if however you have strict
collision check do this".



On 2020-04-11 17:04, Ulrich Mueller wrote:

>> Title: Manual steps required during upgrade to an eselect-free 
>> OpenCL set-up
> 
> Title is too long.

OK, I'll shorten it.

>> We are now in the process of migrating OpenCL in Gentoo to having 
>> all
> 
> Maybe avoid first person?

Can do.

> "eselect-free versions" is a strange term.

How about simply "updated versions"?

> Also, why a line break after "versions"?

It's just because Thunderbird breaks lines at fewer characters than Vim
in text-file mode. It isn't present in the actual news item.

> Another funny line break.

Again, Thunderbird's fault.

>> 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?

I have tried doing this in pkg_preinst but alas, I have found out
collision checks are performed before that function is invoked. I have
also tried setting COLLISION_IGNORE in the replacing package but it
seems that variable only works in make.conf and make.defaults - in which
case it's simpler to simply tell the users to delete those symlinks.

-- 
MS

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to