On 03/22/2018 10:41 AM, 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.
I've already notified Chris gen...@wintermoon.de (I think he maintains it). Is it possible to protect a single file via make.conf ? /opt/brother/scanner/brscan4/brsanenetdevice4.cfg -- Thelma
