Hello Nakamura-san, > About your question, we have implemented Zeroconf support to implement auto > scanner discovery. > However, this is only needed for "epsonds", because "epson2" already has this > feature by the other logic. > i.e. We have accidentally implemented this feature to "epson2" then simply > just remove it. > (In the Release Note, you can find "Undo the improper modification to epson2" > and this means remove Zeroconf implementation from "epson2".)
I understand. I don't have any network based Epson scanner, so I am new
to this topic. Does it mean we maybe have to add this phrase "network
interface supported via DFSG non-free iscan-network-nt package" to the
scanner entries which your patch adds to epson2.desc?
Also, I noticed that your first version has a bugfix for these scanners:
e2_model(s, "ET-16500 Series") || e2_model(s, "L1455 Series") ||
e2_model(s, "EW-M5071FT Series")
However, I couldn't find that these scanners were supported in SANE
upstream or by your patch. I guess this is why these lines were dropped
in the second version?
I already prepared to merge your patch for epson2. I'd just need to know
if we should add the phrase about the iscan package to the desc file.
Thanks and have a nice weekend!
Kind regards,
Wolfram
signature.asc
Description: PGP signature
