[sane-devel] Intended change of config file handling

Johannes Meixner jsmeix at suse.de
Mon Jan 9 13:36:22 UTC 2006


On Dec 28 13:09 Henning Meier-Geinitz wrote (shortened):
> The idea behind this change is that .conf.in files can be preprocessed
> the same way as already done for the manual pages (e.g. sane-epson.man
> -> sane-epson.5). This allows us to use configure variables like
> @DATADIR@ in the config files. The original idea was to use the
> correct firmware directory for scanners which need a firmware in the
> config file automatically.

I do not understand how automated firmware upload should work
if there is more than one scanner connected which use the same
backend but which need different firmware files.

Of course a precondition for automated firmware upload is
that the backend knows the directory where the firmware files
are stored - therefore I appreciate the above change.

But my question is:
Can the backend automatically determine the right firmware file
for a particular model?

If yes, it would be great because then it would be possible to
ask the manufacturers to allow re-distribution of their firmware
files "as is" so that all firmware files for all models of a
backend could be stored in the same firmware directory
and the backend would pick the right one for a particular model.

Kind Regards
Johannes Meixner
SUSE LINUX Products GmbH, Maxfeldstrasse 5      Mail: jsmeix at suse.de
90409 Nuernberg, Germany                    WWW: http://www.suse.de/

More information about the sane-devel mailing list