1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Nel] re: Boost library</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:archer%40nevrax.com">
<LINK REL="Previous" HREF="000098.html">
<LINK REL="Next" HREF="000102.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Nel] re: Boost library</H1>
<B>Vincent Archer</B>
<A HREF="mailto:archer%40nevrax.com"
TITLE="[Nel] re: Boost library">archer@nevrax.com</A><BR>
<I>Fri, 5 Jan 2001 10:39:53 +0100</I>
<P><UL>
<LI> Previous message: <A HREF="000098.html">[Nel] re: Boost library</A></li>
<LI> Next message: <A HREF="000102.html">[Nel] re: Boost library</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#101">[ date ]</a>
<a href="thread.html#101">[ thread ]</a>
<a href="subject.html#101">[ subject ]</a>
<a href="author.html#101">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>According to Bernard Hugueney:
><i> I think there is a misunderstanding. They exclude GPL and LGPL for
</I>><i> library SUBMITTED. They want more of a BSD kind I think. You could not
</I>><i> submit Nel for Boost acceptance,
</I>
Well, the same problem applies in the reverse. Libraries in Boost are
not covered by a GPL-style license. Which means that they cannot be
lifted verbatim from the Boost collection and incorporated in ours
without a lot of precautions.
Just like someone cannot take a GPL piece of software and turn it into
a BSD-licensed software, one cannot lift a BSD-style software and put it
into a GPL project. The licenses are "orthogonal" in style, and you
cannot decide on your own to alter the license; only the copyright owner
may do so.
The license styles from Boost (the ones I've looked at so far, boost.org
is unresolvable at the moment) would prevent us from incoporating them
in NeL. We *might* be able to use them side-by-side, asking people to get
them (and provide mirrors) and compile them separately, but they cannot
be *part* of NeL.
><i> <Quote>
</I>><i> * Must grant permission to copy, use and modify the software for any
</I>><i> use (commercial and non-commercial) for no fee.
</I>><i> </Quote>
</I>><i>
</I>><i> You cannot say that you are not allowed to use a library with such a
</I>><i> licence (Note: ANY USE ) !!!
</I>
The GPL is better worded in that regard; it says for no fee exceeding
the cost of support and shipping (meaning I'm am not obliged to *pay* for
*your* copy).
><i> leads them to move slowly at time (network threads are not there yet...), and
</I>><i> their advanced use of C++ clashes with crappy compiler (VC++). But if you
</I>
Well, we also have to use VC++. The compiler quirks may drive us crazy
with all its "let's not bother the developper with clarity, I'll guess
what he wants to do" philosophy, but there aren't many useful C++
development environments when you're working on a Windows system.
><i> Happy coding !
</I>><i> Bernard
</I>><i> (kinda jealous not to code for my living)
</I>
Many of us code for a living. We just don't code what we'd really love
to code :)
--
Vincent Archer Email: <A HREF="mailto:archer@nevrax.com">archer@nevrax.com</A>
Nevrax France. Off on the yellow brick road we go!
</pre>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI> Previous message: <A HREF="000098.html">[Nel] re: Boost library</A></li>
<LI> Next message: <A HREF="000102.html">[Nel] re: Boost library</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#101">[ date ]</a>
<a href="thread.html#101">[ thread ]</a>
<a href="subject.html#101">[ subject ]</a>
<a href="author.html#101">[ author ]</a>
</LI>
</UL>
</body></html>
|
