kopia lustrzana https://gitlab.com/sane-project/website
66 wiersze
3.1 KiB
HTML
66 wiersze
3.1 KiB
HTML
|
<!-- received="Thu Apr 22 21:49:34 1999 PDT" -->
|
||
|
<!-- sent="Thu, 22 Apr 1999 21:49:34 -0700" -->
|
||
|
<!-- name="David Mosberger-Tang" -->
|
||
|
<!-- email="David.Mosberger@acm.org" -->
|
||
|
<!-- subject="Re: Star Office and scanner" -->
|
||
|
<!-- id="199904230449.VAA03298@panda.mostang.com" -->
|
||
|
<!-- inreplyto="Pine.LNX.3.96.990423011230.10563C-100000@chef.ecs.soton.ac.uk" -->
|
||
|
<title>sane-devel: Re: Star Office and scanner</title>
|
||
|
<h1>Re: Star Office and scanner</h1>
|
||
|
<b>David Mosberger-Tang</b> (<a href="mailto:David.Mosberger@acm.org"><i>David.Mosberger@acm.org</i></a>)<br>
|
||
|
<i>Thu, 22 Apr 1999 21:49:34 -0700</i>
|
||
|
<p>
|
||
|
<ul>
|
||
|
<li> <b>Messages sorted by:</b> <a href="date.html#313">[ date ]</a><a href="index.html#313">[ thread ]</a><a href="subject.html#313">[ subject ]</a><a href="author.html#313">[ author ]</a>
|
||
|
<!-- next="start" -->
|
||
|
<li> <b>Next message:</b> <a href="0314.html">Tripp Lilley: "Re: Sane config thoughts"</a>
|
||
|
<li> <b>Previous message:</b> <a href="0312.html">David Mosberger-Tang: "Re: Star Office and scanner"</a>
|
||
|
<!-- nextthread="start" -->
|
||
|
<!-- reply="end" -->
|
||
|
</ul>
|
||
|
<!-- body="start" -->
|
||
|
<i>>>>>> On Fri, 23 Apr 1999 01:32:46 +0100 (BST), Nick Lamb <<a href="mailto:njl98r@ecs.soton.ac.uk">njl98r@ecs.soton.ac.uk</a>> said:</i><br>
|
||
|
<p>
|
||
|
Nick> Not true if they're just using SANE to provide backends for a<br>
|
||
|
Nick> proprietary SANE frontend. The standard SANE boilerplate<br>
|
||
|
Nick> includes an explicit exemption for the backends when linked<br>
|
||
|
Nick> statically into a proprietary application.<br>
|
||
|
<p>
|
||
|
True.<br>
|
||
|
<p>
|
||
|
Nick> I think this is (for now) a good decision, because the SANE<br>
|
||
|
Nick> backends mostly work with low-level hardware driver stuff. In<br>
|
||
|
Nick> a differently structured operating system, their functionality<br>
|
||
|
Nick> might well be an OS driver module. So we have no reason to<br>
|
||
|
Nick> deny this functionality to proprietary software developers.<br>
|
||
|
<p>
|
||
|
I for one would love to know what frontend they're using. If it's<br>
|
||
|
their own, great (and we should mention it on the web page).<br>
|
||
|
<p>
|
||
|
Nick> NB Although *linking* the backends to proprietary software is<br>
|
||
|
Nick> allowed, the GPL remains in force in every other way. If they<br>
|
||
|
Nick> find a HP bug and fix it in their static binary, they must<br>
|
||
|
Nick> provide source code for the fixed HP backend in order to be<br>
|
||
|
Nick> permitted to distribute it. More likely they'll choose to send<br>
|
||
|
Nick> the HP developer a fix, and ask that he integrate it...<br>
|
||
|
<p>
|
||
|
Correct. Note that the frontends are straight GPL (no exceptions),<br>
|
||
|
however.<br>
|
||
|
<p>
|
||
|
--david<br>
|
||
|
<p>
|
||
|
<pre>
|
||
|
--
|
||
|
Source code, list archive, and docs: <a href="http://www.mostang.com/sane/">http://www.mostang.com/sane/</a>
|
||
|
To unsubscribe: echo unsubscribe sane-devel | mail <a href="mailto:majordomo@mostang.com">majordomo@mostang.com</a>
|
||
|
</pre>
|
||
|
<!-- body="end" -->
|
||
|
<p>
|
||
|
<ul>
|
||
|
<!-- next="start" -->
|
||
|
<li> <b>Next message:</b> <a href="0314.html">Tripp Lilley: "Re: Sane config thoughts"</a>
|
||
|
<li> <b>Previous message:</b> <a href="0312.html">David Mosberger-Tang: "Re: Star Office and scanner"</a>
|
||
|
<!-- nextthread="start" -->
|
||
|
<!-- reply="end" -->
|
||
|
</ul>
|