[olsr-dev] snprintf(), ...
Bernd Petrovitsch
(spam-protected)
Mon Nov 7 11:46:30 CET 2005
On Mon, 2005-11-07 at 11:06 +0100, Thomas Lopatic wrote:
> [adding source code for snprintf() to the olsrd source code]
[...]
> > A license compatible to the olsrd license is enough since the simple
> > integration is "put the source into the tree and add a #define for it".
> > I have to take a closer look into the Makefile to see what's the
> > simplest solution.
>
> Wait a second... Is this really the case? Would we (or other people) be
> allowed to distribute binary-only versions for, for example, Windows if we
> used a GPLed implementation of snprintf() in olsrd?
Probably no. What does the license.txt actually mean? BSD-like?
And it is actually an interesting question: Am I forced to provide the
source code if the only GPL source is in a separate .c and .h file but
actually the code is not present in the compiled (and handed out) output
because the program links aginst a (system-)library which provides the
desired function(ality).
> Hmmm. Maybe we should simply use OpenBSD's implementation. We'd then
> probably have the world's safest snprintf() in olsrd. :-) And it would
Yes, we all know about the bugs in (OpenBSDs original) openssh years
ago;-)
> come with a BSD license.
I don't care *which* one (as long as I don't have to write one).
Bernd
--
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and Services
More information about the Olsr-dev
mailing list