libsane-dev lacks sanei.h header required by some scanner drivers

Bug #1547870 reported by Bartłomiej Żogała
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sane-backends (Ubuntu)
New
Undecided
Unassigned

Bug Description

After installing libsane-dev in /usr/include/sane/ there are sane.h and saneopts.h files but not sanei.h file which is required by some packages. Eg. Canon DR_2020U driver here http://software.canon-europe.com/software/0045134.asp .

The problems covers more header files, at least: sanei_net.h, sanei_wire.h, sanei_usb.h, config.h, sanei_codec_bin.h, sanei_backend.h, sanei_debug.h, sanei_config.h.

All those are present in include/sane directory of sane-backends git source but not in /usr/include/sane after installing libsane-dev or libsane-extras-dev

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: libsane-dev 1.0.25+git20150528-1ubuntu2
ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
Uname: Linux 4.2.0-27-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Feb 20 14:51:31 2016
InstallationDate: Installed on 2015-05-08 (288 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: sane-backends
UpgradeStatus: Upgraded to wily on 2015-11-15 (96 days ago)

Revision history for this message
Bartłomiej Żogała (nusch) wrote :
description: updated
Revision history for this message
Olaf Meeuwissen (olaf.meeuwissen) wrote :

Please note that all `sanei*` files are for internal use by the sane-backends package only. These files are *not* intended to be shared in any way outside of the scope of sane-backends.

If third party backends want to reuse some of these files that is their decision and that's fine buty they should include (and maintain) their own copies. The SANE project does not and will not guarantee any kind of API/ABI compatibility for what's in the `sanei*` files.

None of the `sanei*.h` header files belong in a `libsane-dev` package and I suggest to close this bug report as a "Won't fix".

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.