"m. allan noah" <kitno455 at gmail.com> writes: > [snip} > so, is our answer to Mengqiang that there are only four choices? > > 1. you can write an entirely free backend, and use code from SANE. > > 2. you can write a partly free backend, that runs the closed parts as > a separate process, and use code from SANE in the free part, provided > that the interface to the closed parts is simple and well documented. > > 3. you can write a partly free backend, that dynamically links to the > closed parts, provided that you place a license exception in the free > part allowing said linking. you cannot use any code from SANE, other > than sane.h and the sane specification, in either part.
In the interest of consistency, sane/saneopts.h may be used as well. > 4. you can write an entirely closed backend. you cannot use any code > from SANE, other than sane.h and the sane specification. > > Note that Mengqiang's original suggestion of having a combined library > (or even collection of libs) that has some SANE code in it is > specifically not allowed? Hope this helps, -- Olaf Meeuwissen FLOSS Engineer -- AVASYS Corporation FSF Associate Member #1962 sign up at http://member.fsf.org/
