When emerging the sane-backen one can use epson and/or epson2 by use flags. This will result in sane-epson and sane-epson2 backends. To make this work those backends must be properly listed in the dll.conf file, which will point to epson2 regardless of the use flaggs. I would expect that the the dll.conf should list the epson backends chosen by USE flags. It is possible (by a single try) to list both backends although scanimage -L lists my scanner twice. Reproducible: Always Steps to Reproduce: 1. Set SANE_BACKENDS="epson" 2. Emerge sane-backends Actual Results: Sane will not desover epson scanners, the backend assumes that epson2 is used in favour to epson. The well working scanner will cease to work du to an upgrade (and wife will get annoyed, but that's MY problem ;) ) Expected Results: The config.dll lists the backends selected by use-flags. If both epson and epson2 is added to use flags, the epson2 takes priority and is listed. It might be possible to list both epson and epson2 in the dll.config and instead mark the epson and epson2 USE flags as mutual. This would probably result in similar behaviour but for those where it matters it will be less open to personal modifications. This bug is marked major as the actual result is that the epson scanner suddenly is broken when sane-backedns is updated.
The epson backend is unmaintained and its functionality overlaps with the epson2 backend. So I think it's reasonable to disable "epson" by default. Regarding the bug severity, I can not agree. Your scanner does not stop working as soon as you upgrade, it just stops working as soon as you overwrite the config-protected dll.conf file which does not happen automatically by default. So I tend to leave the package as it is - if you can't tell me a better reason to change it, sorry. Please re-open if you disagree.
