It appears that a user would find it impossible to make any HP scanner on a SANE server visible to a client running SANE. This seems to be a very unfortunate decision to implement.
The localOnly condition was removed in 2007 with the remark:
> This looks like a case where we don't necessarily follow
> the Sane specification. Since the old hpaio code ignored localOnly
> and seemed to work ok, I see no reason for not changing it back.
What is strange is that is was reintroduced in 2013. There is absolutely no record giving details as to why; that it happened and for what reason is not even recorded. This is two years after the Redhat bug mentioned above, which, as far as I can make out, introduced a patch to Redhat only.
So, what is the benefit of not making scanning devices visible on the network through SANE?
We have a bug report in Debian on the same issue:
https:/ /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 807427
It appears that a user would find it impossible to make any HP scanner on a SANE server visible to a client running SANE. This seems to be a very unfortunate decision to implement.
The localOnly condition was removed in 2007 with the remark:
> This looks like a case where we don't necessarily follow
> the Sane specification. Since the old hpaio code ignored localOnly
> and seemed to work ok, I see no reason for not changing it back.
What is strange is that is was reintroduced in 2013. There is absolutely no record giving details as to why; that it happened and for what reason is not even recorded. This is two years after the Redhat bug mentioned above, which, as far as I can make out, introduced a patch to Redhat only.
So, what is the benefit of not making scanning devices visible on the network through SANE?
Regards,
Brian.