Hello all,
After stepping through the SANE 1.05 documentation and the code, I see that code (plus a few platform headers that I may have missed in this missed) consists of only * ddl.c - sane/config.h - lalloca.h - sane/sane.h - sane/sanei.h - sane/sanei_backend.h - sane/sanei_config.h * backend/net.c - sane/config.h - lalloca.h - _stdint.h (???) - sane/sane.h - sane/sanei.h - sane/sanei_net.h * sane/sanei_wire.h - sane/sanei_backend.h - sane/sanei_config.h Everything else seems to be either SANE internal API (used by vendor specific backends/frontends) or vendor specific files. If this is not correct and there are other parts of the SANE code base that should be include the LSB 5.0, please send me a note. Glen ________________________________ From: Petrie, Glen Sent: Monday, March 05, 2012 8:51 AM To: 'sane-devel at lists.alioth.debian.org' Cc: Petrie, Glen Subject: SANE in LSB 5.0 Hello All, I work for Epson (in the US). Epson Japan has requested that I champion the integration of SANE into LSB 5.0. SANE integration in the LSB has been started before; but I hoping to see it through to completion this time. I have already started a dialog with the LSB 5.0 team and I have reviewed the existing SANE material; however, I would like to get any comments, suggestion and help from the members of this mailing list since you have a greater involvement. As I see it, the part of SANE that would become part of the LSB is basically the SANE library and APIs associated with the dll.c, etc code. While there is a lot of vendor instantiated libraries for SANE-Backends and some related to SANE-Frontends; they would not become part of LSB 5.0 unless you can identify generic (non-vendor specific) API for the backend/frontend that need to be included in the LSB. As I go forward the LSB integration process, I will make every attempt to keep this group (mail-list) informed. Glen -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20120316/e824839f/attachment-0001.html>
