| 1 |
On 03/22/2018 10:51 AM, Dale wrote: |
| 2 |
> Neil Bothwick wrote: |
| 3 |
>> On Thu, 22 Mar 2018 11:36:37 -0500, Dale wrote: |
| 4 |
>> |
| 5 |
>>>> It was overwritten because that directory is not part of |
| 6 |
>>>> CONFIG_PROTECT, hardly surprising as that is not a standard |
| 7 |
>>>> configuration location. If the device can't be configured from a file |
| 8 |
>>>> in /etc the ebuild needs to back up the configuration before |
| 9 |
>>>> installing the new version, so file a bug with the overlay. |
| 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 |
>> I imagine that would prevent the new driver being installed too. The |
| 14 |
>> problem appears to stem from having the binary and configuration file in |
| 15 |
>> the same directory. |
| 16 |
>> |
| 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 |
|
| 31 |
Here is a link to this ebuild: |
| 32 |
https://github.com/stefan-langenmaier/brother-overlay/blob/master/media-gfx/brother-scan4-bin/brother-scan4-bin-0.4.4-r4.ebuild |
| 33 |
|
| 34 |
The installation is done via rpm, that is why. |
| 35 |
|
| 36 |
-- |
| 37 |
Thelma |
Archives