| 1 |
On 03/22/2018 10:41 AM, Neil Bothwick wrote: |
| 2 |
> On Thu, 22 Mar 2018 11:36:37 -0500, Dale wrote: |
| 3 |
> |
| 4 |
>>> It was overwritten because that directory is not part of |
| 5 |
>>> CONFIG_PROTECT, hardly surprising as that is not a standard |
| 6 |
>>> configuration location. If the device can't be configured from a file |
| 7 |
>>> in /etc the ebuild needs to back up the configuration before |
| 8 |
>>> installing the new version, so file a bug with the overlay. |
| 9 |
> |
| 10 |
>> Couldn't that location be added in make.conf? As you pointed out, it |
| 11 |
>> shouldn't be there but since it is, maybe protection can be added to |
| 12 |
>> prevent future issues. |
| 13 |
> |
| 14 |
> I imagine that would prevent the new driver being installed too. The |
| 15 |
> problem appears to stem from having the binary and configuration file in |
| 16 |
> the same directory. |
| 17 |
|
| 18 |
I've already notified Chris gentoo@××××××××××.de (I think he maintains it). |
| 19 |
|
| 20 |
Is it possible to protect a single file via make.conf ? |
| 21 |
/opt/brother/scanner/brscan4/brsanenetdevice4.cfg |
| 22 |
|
| 23 |
-- |
| 24 |
Thelma |
Archives