Hello,
On Oct 29 20:13 Stef wrote (excerpt):
- drop support for parallel port scanners
rather than dropping support for working hardware
(and which doesn't require any work), I'd prefer
an option to optionally compile them in (or out).
That would give the package builder the final choice
and keep support for them for those who still use
them (still got 2 of them).
See what I had written here:
--------------------------------------------------------------
Date: Wed, 21 Oct 2015 13:43:17 +0200 (CEST)
...
Subject: Re: [sane-devel] 1.0.25 is out, now what?
.
.
.
My current plan how to drop it is to keep the backends
for parallel port scanners but to only remove the
entries for parallel port scanners from the description
files which results that the YaST scanner setup no longer
shows parallel port scanners. This way I could get end-user
feedback if parallel port scanners are still of any interest
and if yes, I could tell the user how to enable the matching
backend manually without the need to install a different
sane-backends package to get a parallel port scanner working.
--------------------------------------------------------------
I.e. I have no plans to remove the actual backends
(driver libraries) all of a sudden.
Kind Regards
Johannes Meixner
--
SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard,
Graham Norton - HRB 21284 (AG Nuernberg)
--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-requ...@lists.alioth.debian.org
