[sane-devel] making scanbd work OOTB in debian - question about supported backends
wilhelm.wm.meier at googlemail.com
Sat Feb 28 08:27:31 UTC 2015
Am 25.02.2015 um 07:06 schrieb Rolf Leggewie:
> I am maintaining scanbd in Debian and found scanbd difficult to
> configure with lots of possible pitfalls. As much as possible I want to
> make it easy and failproof for the ordinary users to install and use
> scanbd OOTB.
> One of the things that broke things for me and that were hard to
> troubleshoot (I wrote to this ML about it last year) is that the SANE
> backend configurations need to be present both in /etc/sane.d and
> /etc/scanbd. This is due to the nature scanbd sits on top of SANE. I
> still wonder if scanbd couldn't be made to have an explicit
> SANE_BACKEND_CONFIG_DIR in addition to the SANE_CONFIG_DIR?! That would
> eliminate the need for what I am about to explain.
What should be the effect of this env-variable SANE_BACKEND_CONFIG_DIR?
I think it would be best, if the SANE lib would support setting
explicitly the config file (dll.conf) and / or the config dir.
Then saned could use this and introduced a -c <config-file> and / or
-d<dir> options. And in turn scanbd can make use of this.
> During installation of the binary package, I intend to create links from
> all the relevant backends /etc/sane.d/*.conf to /etc/scanbd. I don't
> think all backends have scanner buttons. I cannot imagine the v4l
> backend having scanner buttons (what does it do anyhow?) Same goes for
> the test backend. Would you advise to keep a positive list of which
> backends to include in the linking or rather of which ones to exclude
> (such as dll.conf which is not a backend configuration at all).
> QUESTION: Can anyone point me to which backends have and don't have
> scanner buttons?
More information about the sane-devel