From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] license info for buildroot
Date: Fri, 08 May 2009 09:20:50 +0200 [thread overview]
Message-ID: <87tz3wawml.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <BLU143-W181C7B250C892039D3235DCA640@phx.gbl> (Live Coder's message of "Thu\, 7 May 2009 21\:33\:29 -0700")
>>>>> "Live" == Live Coder <livecoder@live.com> writes:
Live> uClibc contains a link to GPLv3 whereas the downloaded tarball contains GPLv2
Live> license http://git.uclibc.org/uClibc/tree/COPYING.LIB
It's afaik v2, but check with the uclibc developers on the uclibc
list.
Live> Similarly, the buildroot webpage contains a ref to GPLv3 but the
Live> download itself does not contain any license info. Can someone confirm the
Live> actual license is v2 or v3?
It is both (gplv2 or later) - See Makefile. (notice though that we do
include Kconfig from the Linux kernel which is afaik GPLv2 only).
I'll fix the link on the website.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2009-05-08 7:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 4:33 [Buildroot] license info for buildroot Live Coder
2009-05-08 5:24 ` Hans-Christian Egtvedt
2009-05-08 5:53 ` Thiago A. Corrêa
2009-05-08 7:26 ` Peter Korsgaard
2009-05-08 7:24 ` Peter Korsgaard
2009-05-08 7:20 ` Peter Korsgaard [this message]
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=87tz3wawml.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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