| 1 |
On 03/22/2018 10:57 AM, Neil Bothwick wrote: |
| 2 |
> On Thu, 22 Mar 2018 10:50:44 -0600, thelma@×××××××××××.com wrote: |
| 3 |
> |
| 4 |
>>>> Couldn't that location be added in make.conf? As you pointed out, it |
| 5 |
>>>> shouldn't be there but since it is, maybe protection can be added to |
| 6 |
>>>> prevent future issues. |
| 7 |
>>> |
| 8 |
>>> I imagine that would prevent the new driver being installed too. The |
| 9 |
>>> problem appears to stem from having the binary and configuration file |
| 10 |
>>> in the same directory. |
| 11 |
>> |
| 12 |
>> I've already notified Chris gentoo@××××××××××.de (I think he maintains |
| 13 |
>> it). |
| 14 |
>> |
| 15 |
>> Is it possible to protect a single file via make.conf ? |
| 16 |
>> /opt/brother/scanner/brscan4/brsanenetdevice4.cfg |
| 17 |
> |
| 18 |
> man make.conf says yes. |
| 19 |
|
| 20 |
Yes, it worked: |
| 21 |
CONFIG_PROTECT="/opt/brother/scanner/brscan4/brsanenetdevice4.cfg" |
| 22 |
|
| 23 |
after emerging I got a message: |
| 24 |
* IMPORTANT: config file '/opt/brother/scanner/brscan4/brsanenetdevice4.cfg' needs updating. |
| 25 |
|
| 26 |
-- |
| 27 |
Thelma |
Archives