On 03/22/2018 10:51 AM, Dale wrote: > Neil Bothwick wrote: >> On Thu, 22 Mar 2018 11:36:37 -0500, Dale wrote: >> >>>> It was overwritten because that directory is not part of >>>> CONFIG_PROTECT, hardly surprising as that is not a standard >>>> configuration location. If the device can't be configured from a file >>>> in /etc the ebuild needs to back up the configuration before >>>> installing the new version, so file a bug with the overlay. >>> Couldn't that location be added in make.conf? As you pointed out, it >>> shouldn't be there but since it is, maybe protection can be added to >>> prevent future issues. >> I imagine that would prevent the new driver being installed too. The >> problem appears to stem from having the binary and configuration file in >> the same directory. >> >> > > Then there is that. One would think the config file would be in /etc > for a printer/scanner. As you pointed out, that is the logical place > for it to go. I wonder, does the software even look in /etc first and > then in /opt/***? For example, on first use of KDE, it reads a default > file from /usr somewhere and then copies that to the users home > directory. Maybe the driver should or can do that with /etc, instead of > /home of course. In other words, take the file from /opt and stick it > somewhere in /etc that it looks for it and is protected in the future. > > Just thinking out loud to see if something pokes a fix that doesn't come > back to bite later. ;-)
Here is a link to this ebuild: https://github.com/stefan-langenmaier/brother-overlay/blob/master/media-gfx/brother-scan4-bin/brother-scan4-bin-0.4.4-r4.ebuild The installation is done via rpm, that is why. -- Thelma
