Bob Friesenhahn <bfrie...@simple.dallas.tx.us> wrote:
> On Mon, 20 Apr 2009, Tim wrote:
> >
> > Oracle: It should be an interesting ride to say the least. I guess we'll
> > see just how much they love linux... either zfs et. all will become GPL, or
> > we'll see their true colors. I'm secretly hoping for the latter (as long as
> > they keep it open sourced).
>
> I don't think that GPL would be very wise, although a dual-license
> may be ok. Linux would need GPLv2, which is now out of date.
Dual licensing is a general problem as you might see e.g. GPL-only patches that
we cannot use for OpenSolaris.
Do you really like Sun to be forced to verify that the kind of such a patch is
below
the interlectual creation level to be able to claim a copyright?
BTW: GPLv2 is still more open for license combinations than GPLv3 is.
While both GPLv2 and GPLv3 distinct bewteen "the work" and "the complete
source", GPLv2 does not say anything about the license of the rest of the code.
GPLv3 requires "the complete source" to be under GPLv3. This is a real
problem as:
- The term complete source is explained in a way that may include
compilers, editors, revision control systems. You will have to
include them under GPLv3 if a you meet an unhappy author.
- The term "system library" is limited in GPLv3 and does not even
match all libraries that are usually part of the OS installation.
- While GPLv2 results in a general compatibility with any independently
developed library (because it is not part of "the work"), GPLv3 list
only a few exceptions (note that the so called GPLv2 system exception
only allows you to exclude code from "the complete source" but does not
affect license compatibility).
- All other licenses are explicitely excluded from GPLv3 compatibility.
A LGPL-2.1 library that is part of the installation but does not match
the "system library" criteria of the GPLv3 cannot be used from a GPLv3
program.
Conclusion: GPLv3 creates more problems than it solved. If you like to think
about other licenses, you better stay with GPLv2.
Jörg
--
EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
j...@cs.tu-berlin.de (uni)
joerg.schill...@fokus.fraunhofer.de (work) Blog:
http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
