From: Mike Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] [Question] Is it ok to change Buildroot for own needs?
Date: Fri, 9 May 2014 10:18:26 -0500 [thread overview]
Message-ID: <20140509101826.107d7f42@core2quad.morethan.org> (raw)
In-Reply-To: <536CA3D7020000460004F5B8@gwia2.rz.hs-offenburg.de>
On Fri, 09 May 2014 09:45:59 +0200
"Frank Ihle" <frank.ihle@hs-offenburg.de> 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 ?
>
Yes.
And if you intend to submit your changes to the Buildroot project, the
best way.
If you intend to keep your changes private (because they are
proprietary or some other reason) -
Then you best choice is to put them in the BR2_EXTERNAL tree.
That leaves the project tree un-modified (easier to get support for
any problems with that part) and your "private" additions in the
BR2_EXTERNAL sub-tree of your project.
Mike
> Kind Regards
>
> Frank
>
next prev parent reply other threads:[~2014-05-09 15:18 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 [this message]
2014-05-09 20:47 ` Arnout Vandecappelle
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=20140509101826.107d7f42@core2quad.morethan.org \
--to=minimod@morethan.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