unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Михалева, Екатерина" <e.mihaleva@my.mgimo.ru>
To: help-guix@gnu.org
Subject: Asking for clarifications
Date: Tue, 9 Mar 2021 21:03:02 +0300	[thread overview]
Message-ID: <CAPUAKLZiY9MfamAWvta_uBg+P-BxnW=6bDF_eHmNXREux6Ex4g@mail.gmail.com> (raw)

To whom it may concern,

My name is Ekaterina Mikhaleva, I am a young researcher and a PhD student,
majoring in IT/IP law.

I would like to clarify how is it possible that the Guix System that is a
free GNU/Linux distribution acknowledged by the FSF uses Linux kernel,
which is licensed under GPLv2, and at the same time Guix System is licensed
under GPLv3?
I am a specialist in law, so I cannot probably grasp all the technical
peculiarities, though I have checked on your website in the "Packages"
section any mentioning on Linux kernel and here
https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/linux.scm#n3138
 I found the following:

   (home-page "https://www.gnu.org/software/linux-libre/")
    (synopsis "GNU Linux-Libre kernel headers")
    (description "Headers of the Linux-Libre kernel.")
    (license license:gpl2)))


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?

I will be immensely grateful for your clarifications.

Thank you in advance.

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-09 18:03 Михалева, Екатерина [this message]
2021-03-10 23:21 ` Asking for clarifications divoplade
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='CAPUAKLZiY9MfamAWvta_uBg+P-BxnW=6bDF_eHmNXREux6Ex4g@mail.gmail.com' \
    --to=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).