question about proprietary libraries
- To: debian-mentors <email@example.com>
- Subject: question about proprietary libraries
- From: Stephen Sinclair <firstname.lastname@example.org>
- Date: Wed, 1 Sep 2010 20:40:39 -0400
- Message-id: <AANLkTi=k5pYO6j4843t_-GiyNsrBOreSBN4=xtQqj1Tk@mail.gmail.com>
This is a general question about linking to proprietary libraries.
Specifically I am thinking about developing a library which will work
normally in the general case, but in some cases the user might have a
proprietary library installed on their system, in which case I'd like
to dynamically load that library and call out to its functions.
The proprietary library in this case would be for doing I/O with a
particular hardware device, for which there is currently no open
source alternative. Therefore the user owning such a device would
have installed the software and expect my library to work with it.
Conversely, he would not have the proprietary library unless he has
the device in question.. so I sort of think of this library as being
"part of" the device. I don't have the ability to reverse engineer it
and write my own drivers, but I'd still like users of this device to
be able to make use of my software.
Would such a library have difficulty getting accepted by Debian?
Are there other examples of libraries in Debian which optionally
leverage proprietary code if it is available?