Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [V4 1/1] python-mutagen: new package
Date: Thu, 26 Jan 2017 21:35:44 +1300	[thread overview]
Message-ID: <20170126213544.63e1d65c@free-electrons.com> (raw)
In-Reply-To: <CAGm1_kvv333QSzgkE2iaeJ89Z48xJAVcSK+qSD2VaTr89bANeA@mail.gmail.com>

Hello,

On Thu, 26 Jan 2017 09:15:52 +0100, Yegor Yefremov wrote:

> This is the stuff I still don't really grok. How do I tell whether it
> is GPLv2 or GPLv2+?
> 
> This passage [1] contains such a sentence:
> 
> "either version 2 of the License, or (at your option) any later version."

Have you read this part of the license? It is an *example* of what you
can put in the header of your files to indicate what the license is.

So this part of the license is an *example*, it does not tell you at
all what is the license that applies to this package.

To know whether it's GPLv2 or GPLv2+ you have to open an actual source
file, and look at its copyright header. If it says "version 2 or
later", then it's GPLv2+. If it says "version 2", then it's GPLv2 only.

If you look at the mutagen source code, all source files I could see
mention just "version 2", hence GPLv2.

Please read again the text of the GPL around the line you indicated.
You will understand better what it means.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-01-26  8:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25 16:26 [Buildroot] [V4 1/1] python-mutagen: new package Adam Duskett
2017-01-26  8:08 ` Thomas Petazzoni
2017-01-26  8:15   ` Yegor Yefremov
2017-01-26  8:35     ` Thomas Petazzoni [this message]
2017-01-26  8:41       ` Yegor Yefremov

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

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

  git send-email \
    --in-reply-to=20170126213544.63e1d65c@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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