Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] License for patches
Date: Wed, 24 Aug 2011 16:14:28 +0000 (UTC)	[thread overview]
Message-ID: <j33814$hoj$1@dough.gmane.org> (raw)
In-Reply-To: 201108241205.23310.vapier@gentoo.org

On 2011-08-24, Mike Frysinger <vapier@gentoo.org> wrote:
> On Wednesday, August 24, 2011 11:25:20 Lars Reemts wrote:

>> Which license is relevant for the package specific patches distributed
>> by buildroot? Formally it must be the GPL.
>
> says who ?  i dont see the logic here.

According to http://buildroot.uclibc.org/:

  Buildroot is a set of Makefiles and patches [....]
  
  Buildroot is [...] licensed under the GNU GENERAL PUBLIC LICENSE V2
  (Or later).

Seems pretty clear to me: the patches are under the GPL.

The question is what happens when you combine GPL'd source (the
patches) with original source that's not under GPL.  It seems like a
very legitimate question.

-- 
Grant Edwards               grant.b.edwards        Yow! Let's send the
                                  at               Russians defective
                              gmail.com            lifestyle accessories!

  reply	other threads:[~2011-08-24 16:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24 15:25 [Buildroot] License for patches Lars Reemts
2011-08-24 16:05 ` Mike Frysinger
2011-08-24 16:14   ` Grant Edwards [this message]
2011-08-24 16:55     ` Yann E. MORIN
2011-08-24 20:48       ` Peter Korsgaard
2011-08-24 17:13     ` Mike Frysinger
2011-08-24 17:38       ` Grant Edwards
2011-08-24 18:08         ` Mike Frysinger
2011-08-24 20:47       ` Peter Korsgaard
2011-08-29 12:32         ` Thomas Petazzoni
2011-08-24 16:21   ` Robin Holt

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='j33814$hoj$1@dough.gmane.org' \
    --to=grant.b.edwards@gmail.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