From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [Question] Is it ok to change Buildroot for own needs?
Date: Fri, 09 May 2014 22:47:06 +0200 [thread overview]
Message-ID: <536D3ECA.9050905@mind.be> (raw)
In-Reply-To: <536CA3D7020000460004F5B8@gwia2.rz.hs-offenburg.de>
On 09/05/14 09:45, Frank Ihle wrote:
> Hi everyone,
>
> I'm not a Pro, when it comes to the license of someone's other Software.
> Basically I'd like to add a new menu that includes some of the Target packages.
> Is it ok for "Buildroot" if i change it like this ?
Buildroot is under the GPL license. That means you are allowed to modify it in
any way that you want. However, if you redistribute (= give it to someone else
in any way) buildroot, you have to:
* also give the source (of buildroot, not necessarily of the packages;
* indicate that you've modified buildroot.
Redistributing the generated images doesn't count as redistributing buildroot
(at least we don't think it does). However, if the generated image contains any
GPL software, e.g. busybox, then *that* license also requires you to provide the
source of busybox, as well as any scripts required to build it. We think that
buildroot is such a script. In other words, when you redistribute the images and
it contains GPL software, we think that you have to provide your modified source
of buildroot as well.
Note that I'm not a lawyer and none of this has a precedent in court AFAIK.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2014-05-09 20:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 7:45 [Buildroot] [Question] Is it ok to change Buildroot for own needs? Frank Ihle
2014-05-09 15:18 ` Mike Zick
2014-05-09 20:47 ` Arnout Vandecappelle [this message]
2014-05-12 7:43 ` Frank Ihle
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=536D3ECA.9050905@mind.be \
--to=arnout@mind.be \
--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