unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: divoplade <d@divoplade.fr>
To: "Михалева, Екатерина" <e.mihaleva@my.mgimo.ru>, help-guix@gnu.org
Subject: Re: Asking for clarifications
Date: Thu, 11 Mar 2021 00:21:38 +0100	[thread overview]
Message-ID: <d11f6d7cf5d368b1648d959dbae173067b23e306.camel@divoplade.fr> (raw)
In-Reply-To: <CAPUAKLZiY9MfamAWvta_uBg+P-BxnW=6bDF_eHmNXREux6Ex4g@mail.gmail.com>

Hello,

Le mardi 09 mars 2021 à 21:03 +0300, Михалева, Екатерина a écrit :
> As far as I know, GPLv2 and GPLv3 are incompatible and Linux kernel
> is
> licensed strictly under GPLv2 without any possibility to update to
> any
> further version.
> I presumed that GPLv2 would make the whole product subject to the
> term of
> this particular license. Still your product is licensed under GPLv3,
> if I
> am correct?

In my limited understanding of what is happening, Guix is not a
derivative work of Linux (a "covered work" according to the GPL, so a
work based on Linux) because it does not use the source code of Linux.
If you were to write a module for Linux (e.g. a driver), it would use a
lot of the non-trivial internal APIs, code and data structures defined
by and for the kernel, so it would be considered a covered work and you
would need to use GPLv2. But this is not the case for Guix.

I’m still looking for more specific answers, though.



  reply	other threads:[~2021-03-10 23:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-09 18:03 Asking for clarifications Михалева, Екатерина
2021-03-10 23:21 ` divoplade [this message]
2021-03-11  8:12 ` Ricardo Wurmus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d11f6d7cf5d368b1648d959dbae173067b23e306.camel@divoplade.fr \
    --to=d@divoplade.fr \
    --cc=e.mihaleva@my.mgimo.ru \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).