[lkml]   [2006]   [Sep]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: GPLv3 Position Statement

    >People don't have a clue!
    >The GPLv2 never _ever_ mentions "linking" or any other technical measure
    >at all. Doing so would just be stupid (another problem with the GPLv3,
    >btw). So people who think that the GPLv2 disallows "linking" with
    >non-GPLv2 code had better go back and read the license again.
    >Grep for it, if you want to. The word "link" simply DOES NOT EXIST IN THE

    Hah then read LICENSE.LGPL!

    """Most GNU software, including some libraries, is covered by the
    ordinary GNU General Public License. This license, the GNU Lesser
    General Public License, applies to certain designated libraries, and
    is quite different from the ordinary General Public License. We use
    this license for certain libraries in order to permit linking those
    libraries into non-free programs."""

    If the GPL does not mention linking at all, and therefore does not
    really forbid it, why do we need an LGPL to allow linking then?

    >What the GPLv2 actually talks about is _only_ about "derived work". And
    >whether linking (dynamically, statically, or by using an army of worker
    >gnomes that re-arrange the bits to their liking) means something is
    >"derived or not" is a totally different issue, and is not something you
    >can actually say one way or the other, because it will depend on the

    I would be of the opinion that dynamic linking does not make it a
    derived work, because neither the ld program nor the
    dynamic linker knows whether -lfoo is actually GPL or not.

    >> No. The definition of a derivative work is a legal one and not a
    >> technical one.

    And that is a major problem IMHO. If there is no definitive
    [technical] answer to what constitues a derived work, and it leaves
    you at risk to lose a case in court while it is a gray area.

    Oh well back on the topic: A userspace app just is not a derivate
    work of the kernel, for me at least.

    >Now, it is also indisputable that if you _need_ to "link", it's a damn
    >good sign that something is _very_likely_ to be derivative, but as Alan
    >points out, you could do the same thing with RPC over a socket, and the
    >fact that you did it technically differently really makes no real
    >difference. So linking per se isn't the issue, and never has been.

    Jan Engelhardt
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2006-09-28 10:09    [from the cache]
    ©2003-2014 Jasper Spaans. hosted at Digital Ocean