Skip to content

Support for out-of-tree Buildroot customization

Yann E. MORIN buildroot 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest0 of 3 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 3 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [Buildroot] [PATCH 0/3] Support for out-of-tree Buildroot customization

Andy, All,

On 2013-09-12 22:28 +0000, ANDY KENNEDY spake thusly:

Quoted 44 lines
Quoted 44 lines

Yann E. MORIN wrote:
IANAL, this is not legal advice, talk to your lawyer.

Here are however my toughts on this:

1- all the Config.in and package.mk files, plus the external.mk file,
and all other files sourced or otherwise included by a file from Buildroot (and thus use Buildroot's infrastructure) could be considered a derived work of Buildroot, and thus must be licensed with a compatible license,
2- the defconfigs could be considered as what the GPL identifies as the
"scripts used to control compilation and installation of the executable", since without the .config file, an end-user can not reproduce the executable(s),
3- everything else might be considered not a derived work of Buildroot,
and might not be required to be licensed with a license compatible with Buildroot's license.

Explanations:

1- It's not because it is to be licensed under a license compatible with
the Buildroot license that it *has* to be distributed. Just that if it *is* distributed, the licensing terms on that should be compatible with Buildroot's licensing terms.

2- That's because Buildroot will most probably build a GPL/LGPL program
that will end up in the ytarget that this applies, because of the license of those programs, not because of Buildroot's license. Even if Buildroot was under a different license, this would still apply as long as a GPL/LGPL program ends up in the target.

3- By "everything else", I mean: a package (in Buildroot's terminology:
the Config.in and associated .mk file) that directly embbeds the source files (.c and .h and ...) for this package (like the host-mkpasswd). These source files can not be considered a derived work of Buildroot, so Buildroot's license does not apply to those.

So, I think the make legal-stuff should descend into BR2_EXTERNAL, as if it was an integral part of Buildroot.

BR2_EXTERNAL is here *just* to separate parts of the recipes from the upstream ones, as a mean to clearly separate local changes from the upstream reference.

Quoted 6 lines
Quoted 1 line

But again: IANAL, this is not legal advice, talk to your legal counsel.

Since tone is difficult to understand through e-mail, please understand that I'm not attempting to start a flame war, nor am I throwing stones. . . just brainstorming (or in my case, perhaps a light shower).

No problem, there are no feelings in my words (OK, just a very little bit!).

Quoted 2 lines

You speak of BuildRoot as a third party. BuildRoot is not really a third party but is first person from my point of view.

No, Buildroot is *not* a third party.

Consider this situation:
Buildroot community

    -> makes Buildroot available under GPLv2

Company FooCorp

    -> uses Buildroot
    -> creates BR2_EXTERNAL
    -> distributes BR2_EXTERNAL

You or Me

    -> gets BR2_EXTERNAL from FooCorp

The third party I referred to (in my other mail) would be "You or Me" here.

Quoted 4 lines

Although I have not added
NEAR as much as other people, I still contend that I am partial owner in BuildRoot. To that end, I have a voice in the decision making over any external (or internal for that matter) infrastructure and/or tie-in.

Yes, but since Buildroot pre-existed under the GPLv2 prior to your changes, and your changes were made explicitly to work with Buildroot (by being modifications to Buildroot), then those changes are GPLv2.

[--SNIP--]
What I'm arguing is that the content of BR2_EXTERNAL that _interacts with Buildroot's internal infrastructure_ *are* a derived work of Buildroot.

Let's take a (very simplistic) example:

    BR2_EXTERNAL/
        package/
            pkg-1/
                Config.in           *
                pkg-1.mk            *
                pkg-1-main.c        -
                pkg-1.h             -

* : a derived work of Buildroot
- : not a derived work of Buildroot

Config.in and pkg-1.mk are clearly (in my opinion) a derived work of Buildroot, since they are written with the very intent to be interacting with Buildroot's internal infrastructure.

But pkg-1-main.c and pkg-1.h (which are the C sources of pkg-1) are *not* a derived work of Buildroot, and thus can well be under whatever license.

Regards,
Yann E. MORIN.

Signature · 6 lines
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'