| 1 |
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 |
>> Couldn't that location be added in make.conf? As you pointed out, it |
| 10 |
>> shouldn't be there but since it is, maybe protection can be added to |
| 11 |
>> prevent future issues. |
| 12 |
> I imagine that would prevent the new driver being installed too. The |
| 13 |
> problem appears to stem from having the binary and configuration file in |
| 14 |
> the same directory. |
| 15 |
> |
| 16 |
> |
| 17 |
|
| 18 |
Then there is that. One would think the config file would be in /etc |
| 19 |
for a printer/scanner. As you pointed out, that is the logical place |
| 20 |
for it to go. I wonder, does the software even look in /etc first and |
| 21 |
then in /opt/***? For example, on first use of KDE, it reads a default |
| 22 |
file from /usr somewhere and then copies that to the users home |
| 23 |
directory. Maybe the driver should or can do that with /etc, instead of |
| 24 |
/home of course. In other words, take the file from /opt and stick it |
| 25 |
somewhere in /etc that it looks for it and is protected in the future. |
| 26 |
|
| 27 |
Just thinking out loud to see if something pokes a fix that doesn't come |
| 28 |
back to bite later. ;-) |
| 29 |
|
| 30 |
Dale |
| 31 |
|
| 32 |
:-) :-) |
Archives