Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] udev-extraconf: change LICENSE to MIT
Date: Tue, 31 Jul 2012 12:26:50 +0100	[thread overview]
Message-ID: <1343734010.9756.3.camel@ted> (raw)
In-Reply-To: <1343674860-1523-1-git-send-email-Martin.Jansa@gmail.com>

On Mon, 2012-07-30 at 21:01 +0200, Martin Jansa wrote:
> * original recipe added by RP in fc128ab1e4fec27d44cebfa690a9bc233eda0caf was saying GPL
> * later it was changed to GPLv2
> * COPYING.GPL was added to reflect that
> * meta-oe has similar recipe with MIT license and even more scripts, so lets change LICENSE here too
> 
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> ---
>  meta/recipes-core/udev/udev-extraconf/COPYING.GPL |  339 ---------------------
>  meta/recipes-core/udev/udev-extraconf_1.0.bb      |    8 +-
>  2 files changed, 4 insertions(+), 343 deletions(-)
>  delete mode 100644 meta/recipes-core/udev/udev-extraconf/COPYING.GPL

Er, I think we need to be a little more careful than this. Just because
you want something to be so, doesn't make it happen just like that...

Looking at the commit, I've just copied the license from the original
source which was a GPLv2 recipe (udev). Where did mount.blacklist come
from originally? Is there evidence its MIT licensed? How did meta-oe
conclude this was MIT licensed?

Cheers,

Richard




  reply	other threads:[~2012-07-31 11:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-30 15:03 [PATCH] udev-extraconf: merge with udev-extra-rules from meta-oe Martin Jansa
2012-07-30 15:12 ` Martin Jansa
2012-07-30 17:42 ` Koen Kooi
2012-07-30 17:59   ` Martin Jansa
2012-07-30 19:01     ` [PATCH] udev-extraconf: change LICENSE to MIT Martin Jansa
2012-07-31 11:26       ` Richard Purdie [this message]
2012-07-31 11:37         ` Martin Jansa
2012-07-31 12:46         ` Koen Kooi
2012-08-30  9:06           ` Martin Jansa
2012-08-05 10:23 ` [PATCH] layer.conf: add udev-extraconf to SIGGEN_EXCLUDERECIPES_ABISAFE Martin Jansa

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=1343734010.9756.3.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@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