From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH v2] dvdauthor-0.6.18: initial recipe
Date: Tue, 19 Oct 2010 20:33:39 +0200 [thread overview]
Message-ID: <4CBDE483.3030002@opendreambox.org> (raw)
In-Reply-To: <AANLkTikVU2M3gEC_Zd4PTPys_Er4x+uU0txYw5BftQVJ@mail.gmail.com>
On 10/19/2010 07:32 PM, Frans Meulenbroeks wrote:
> 2010/10/19 Andreas Oberritter <obi@opendreambox.org>:
>> * v2: updated DESCRIPTION, SECTION and PRIORITY
>>
>> Signed-off-by: Andreas Oberritter <obi@opendreambox.org>
>> ---
>> recipes/dvdauthor/dvdauthor_0.6.18.bb | 13 +++++++++++++
>> 1 files changed, 13 insertions(+), 0 deletions(-)
>> create mode 100644 recipes/dvdauthor/dvdauthor_0.6.18.bb
>>
>> diff --git a/recipes/dvdauthor/dvdauthor_0.6.18.bb b/recipes/dvdauthor/dvdauthor_0.6.18.bb
>> new file mode 100644
>> index 0000000..24f3a74
>> --- /dev/null
>> +++ b/recipes/dvdauthor/dvdauthor_0.6.18.bb
>> @@ -0,0 +1,13 @@
>> +DESCRIPTION = "A set of tools to help you generate DVD files to be played back on a standalone DVD player"
>> +SECTION = "console/multimedia"
>> +PRIORITY = "optional"
>> +LICENSE = "GPLv2"
>
> Have you verified this is v2 and not v2 or later (aka v2+)?
Has there been an agreement on the correct notation of the commonly used
licenses? I don't quite get why making a difference between v2 and v2+
is important for OE, because v2+ can still be distributed as v2, if you
choose to. The only difference is that packages like the Linux kernel
can not be distributed as v3 or later, but what would be the benefit for
OE and its users in that case anyway?
Also, v2 could mean "the original unmodified license v2, which includes
the or-any-later-version-if-specified-in-the-program clause", while v2+
might suggest a modified v2 license.
Then, there was a recent commit, which changed GPL to GPLv2, while the
commit message suggested that GPLv2+ was the dominant license in that
package [1].
Having said that, there are some files in dvdauthor, which contain a
header stating that later versions of the GPL may be used, but not every
file contains such a header. Therefore, the safe choice is to use GPLv2,
which is what COPYING says, because I cannot assume that every file,
which does not include such a header, is safe to distribute under v3 or
later.
Btw.: Debian is very picky about licenses, but does not offer a separate
license file for GPL-v2-but-not-later programs in
/usr/share/common-licenses.
Regards,
Andreas
[1]
http://cgit.openembedded.net/cgit.cgi/openembedded/commit/?h=master&id=860f2947b54a29becb4686261026c205bf3b9358
next prev parent reply other threads:[~2010-10-19 18:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 16:36 [PATCH] dvdauthor-0.6.18: initial recipe Andreas Oberritter
2010-10-19 17:00 ` [PATCH v2] " Andreas Oberritter
2010-10-19 17:32 ` Frans Meulenbroeks
2010-10-19 18:33 ` Andreas Oberritter [this message]
2010-10-19 21:14 ` [PATCH] gedit_2.30.0: Set `LICENSE` to GPLv2+ for real Paul Menzel
2010-10-25 13:00 ` [PATCH v2 resend] dvdauthor-0.6.18: initial recipe Andreas Oberritter
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=4CBDE483.3030002@opendreambox.org \
--to=obi@opendreambox.org \
--cc=openembedded-devel@lists.openembedded.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