| 1 |
thelma@×××××××××××.com wrote: |
| 2 |
> On 03/22/2018 10:51 AM, Dale wrote: |
| 3 |
>> Neil Bothwick wrote: |
| 4 |
>>> On Thu, 22 Mar 2018 11:36:37 -0500, Dale wrote: |
| 5 |
>>> |
| 6 |
>>>>> It was overwritten because that directory is not part of |
| 7 |
>>>>> CONFIG_PROTECT, hardly surprising as that is not a standard |
| 8 |
>>>>> configuration location. If the device can't be configured from a file |
| 9 |
>>>>> in /etc the ebuild needs to back up the configuration before |
| 10 |
>>>>> installing the new version, so file a bug with the overlay. |
| 11 |
>>>> Couldn't that location be added in make.conf? As you pointed out, it |
| 12 |
>>>> shouldn't be there but since it is, maybe protection can be added to |
| 13 |
>>>> prevent future issues. |
| 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 |
>>> |
| 19 |
>> Then there is that. One would think the config file would be in /etc |
| 20 |
>> for a printer/scanner. As you pointed out, that is the logical place |
| 21 |
>> for it to go. I wonder, does the software even look in /etc first and |
| 22 |
>> then in /opt/***? For example, on first use of KDE, it reads a default |
| 23 |
>> file from /usr somewhere and then copies that to the users home |
| 24 |
>> directory. Maybe the driver should or can do that with /etc, instead of |
| 25 |
>> /home of course. In other words, take the file from /opt and stick it |
| 26 |
>> somewhere in /etc that it looks for it and is protected in the future. |
| 27 |
>> |
| 28 |
>> Just thinking out loud to see if something pokes a fix that doesn't come |
| 29 |
>> back to bite later. ;-) |
| 30 |
> Here is a link to this ebuild: |
| 31 |
> https://github.com/stefan-langenmaier/brother-overlay/blob/master/media-gfx/brother-scan4-bin/brother-scan4-bin-0.4.4-r4.ebuild |
| 32 |
> |
| 33 |
> The installation is done via rpm, that is why. |
| 34 |
> |
| 35 |
> -- |
| 36 |
> Thelma |
| 37 |
> |
| 38 |
> |
| 39 |
|
| 40 |
|
| 41 |
At least you found a workaround. Still, one would think it would be in |
| 42 |
/etc. That tends to be the Linux way of things. At least you found a |
| 43 |
solution that prevents it from overwriting your config file. Hopefully |
| 44 |
they won't rename the file now. ;-) |
| 45 |
|
| 46 |
Dale |
| 47 |
|
| 48 |
:-) :-) |
Archives