All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 09/22] manual: add advice about GPL compliance for Buildroot
Date: Thu, 17 May 2012 19:33:08 +0200	[thread overview]
Message-ID: <1337276001-26149-10-git-send-email-luca@lucaceresoli.net> (raw)
In-Reply-To: <1337276001-26149-1-git-send-email-luca@lucaceresoli.net>

Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
---
 docs/manual/using.txt |   27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)

diff --git a/docs/manual/using.txt b/docs/manual/using.txt
index 42d4061..fcbd24b 100644
--- a/docs/manual/using.txt
+++ b/docs/manual/using.txt
@@ -284,3 +284,30 @@ Buildroot, with the name used in the manifest file:
 * +BSD-2c+: BSD 2-clause license;
 * +PROPRIETARY+: marks a non-opensource package;
   Buildroot does not save any licensing info or source code for these packages.
+
+Complying with the Buildroot license
+------------------------------------
+
+Buildroot itself is an opensource software, released under the
+http://www.gnu.org/licenses/old-licenses/gpl-2.0.html[GNU General Public
+License, version 2] or (at your option) any later version.
+However, being a build system, it is not normally part of the end product:
+if you develop the root filesystem, kernel, bootloader or toolchain for a
+device, the code of Buildroot is only present on the development machine, not
+in the device storage.
+
+Nevertheless, the general view of the Buildroot developers is that you should
+release the Buildroot source code along with the source code of other packages
+when releasing a product that contains GPL-licensed software.
+This is because the
+http://www.gnu.org/licenses/old-licenses/gpl-2.0.html[GNU GPL]
+defines the "'complete source code'" for an executable work as "'all the
+source code for all modules it contains, plus any associated interface
+definition files, plus the scripts used to control compilation and installation
+of the executable'".
+Buildroot is part of the 'scripts used to control compilation and
+installation of the executable', and as such it is considered part of the
+material that must be redistributed.
+
+Keep in mind this is only the Buildroot developers' opinion, and you should
+consult your legal department or lawyer in case of any doubt.
-- 
1.7.9.5

  parent reply	other threads:[~2012-05-17 17:33 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17 17:32 [Buildroot] [PATCH v4 00/22] Automatically produce legal compliance info Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 01/22] legal-info: infrastructure to collect legally-relevant material Luca Ceresoli
2012-05-21 21:21   ` Arnout Vandecappelle
2012-05-17 17:33 ` [Buildroot] [PATCH v4 02/22] gettext: warn that legal-info is not implemented Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 03/22] netkitbase: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 04/22] netkittelnet: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 05/22] newt: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 06/22] ttcp: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 07/22] vpnc: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 08/22] manual: document usage of the legal-info feature Luca Ceresoli
2012-05-17 17:33 ` Luca Ceresoli [this message]
2012-05-17 20:56   ` [Buildroot] [PATCH v4 09/22] manual: add advice about GPL compliance for Buildroot Thomas De Schampheleire
2012-05-20 12:37   ` Arnout Vandecappelle
2012-07-05 13:52   ` Luca Ceresoli
2012-07-05 20:23     ` Arnout Vandecappelle
2012-05-17 17:33 ` [Buildroot] [PATCH v4 10/22] linux: define license Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 11/22] m4: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 12/22] mpc: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 13/22] fakeroot: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 14/22] bzip2: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 15/22] directfb: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 16/22] iostat: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 17/22] lzo: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 18/22] lzop: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 19/22] libusb: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 20/22] pcre: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 21/22] netsnmp: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 22/22] berkeleydb: " Luca Ceresoli
2012-06-20 13:07 ` [Buildroot] [PATCH v4 00/22] Automatically produce legal compliance info Luca Ceresoli
2012-07-16 15:55 ` Thomas Petazzoni
2012-07-17 14:55   ` Thomas De Schampheleire
2012-07-17 15:07     ` Maxime Ripard
2012-07-17 15:18       ` Samuel Martin
2012-07-17 17:36 ` Thomas Petazzoni
2012-07-17 18:58   ` Thomas Petazzoni
2012-07-19 10:11     ` Luca Ceresoli
2012-07-19 11:30       ` Thomas Petazzoni

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=1337276001-26149-10-git-send-email-luca@lucaceresoli.net \
    --to=luca@lucaceresoli.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.