All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 08/22] manual: document usage of the legal-info feature
Date: Thu, 17 May 2012 19:33:07 +0200	[thread overview]
Message-ID: <1337276001-26149-9-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/adding-packages-gentargets.txt |   21 ++++++
 docs/manual/using.txt                      |  103 ++++++++++++++++++++++++++++
 2 files changed, 124 insertions(+)

diff --git a/docs/manual/adding-packages-gentargets.txt b/docs/manual/adding-packages-gentargets.txt
index cfcee8c..7a7889e 100644
--- a/docs/manual/adding-packages-gentargets.txt
+++ b/docs/manual/adding-packages-gentargets.txt
@@ -218,6 +218,27 @@ information is (assuming the package name is +libfoo+) :
   You can find some documentation for this syntax in the xref:makedev-syntax[].
   This variable is optional.
 
+* +LIBFOO_LICENSE+ defines the license (or licenses) under which the package
+  is released.
+  This name will appear in the manifest file produced by +make legal-info+.
+  If the license is one of those listed in xref:legal-info[],
+  use the same string to make the manifest file uniform.
+  Otherwise, describe the license in a precise and concise way, avoiding
+  ambiguous names such as +BSD+ which actually name a family of licenses.
+  If the root filesystem you generate contains non-opensource packages, you
+  can define their license as +PROPRIETARY+: Buildroot will not save any
+  licensing info or source code for this package.
+  This variable is optional. If it is not defined, +unknown+ will appear in
+  the +license+ field of the manifest file for this package.
+
+* +LIBFOO_LICENSE_FILES+ is a space-separated list of files in the package
+  tarball that contain the license(s) under which the package is released.
+  +make legal-info+ copies all of these files in the +legal-info+ directory.
+  See xref:legal-info[] for more information.
+  This variable is optional. If it is not defined, a warning will be produced
+  to let you know, and +not saved+ will appear in the +license files+ field
+  of the manifest file for this package.
+
 The recommended way to define these variables is to use the following
 syntax:
 
diff --git a/docs/manual/using.txt b/docs/manual/using.txt
index a5dc9e1..42d4061 100644
--- a/docs/manual/using.txt
+++ b/docs/manual/using.txt
@@ -181,3 +181,106 @@ or +g+++ for building helper-binaries on your host, then do
 --------------------
  $ make HOSTCXX=g++-4.3-HEAD HOSTCC=gcc-4.3-HEAD
 --------------------
+
+Complying with opensource licenses
+----------------------------------
+[[legal-info]]
+
+All of the end products of Buildroot (toolchain, root filesystem, kernel,
+bootloaders) contain opensource software, released under various licenses.
+
+Using opensource software gives you the freedom to build rich embedded
+systems choosing from a wide range of packages, but also gives some
+obligations that you must know and honour.
+Some licenses require you to publish the license text in the documentation of
+your product. Other require you to redistribute the source code of the
+software to those that receive your product.
+
+The exact requirements of each license is documented in each package, and it is
+your (or your legal office's) responsibility to comply with these requirements.
+To make this easier for you, Buildroot can collect for you some material you
+will probably need. To produce this material, after you configured Buildroot
+with +make menuconfig+, +make xconfig+ or +make gconfig+, run:
+
+--------------------
+make legal-info
+--------------------
+
+Buildroot will collect legally-relevant material in your output directory,
+under the +legal-info/+ subdirectory.
+There you will find:
+
+* A +README+ file, that summarizes the produced material and contains warnings
+  about material that Buildroot could not produce.
+* +buildroot.config+: this is the Buildroot configuration file that is usually
+  produced with +make menuconfig+, and which is necessary to reproduce the
+  build.
+* The source code for all packages; this is saved in the +sources/+
+  subdirectory (except for proprietary packages, whose source code is not
+  saved);
+  patches applied to some packages by Buildroot are distributed with the
+  Buildroot sources and are not duplicated in the +sources/+ subdirectory.
+* A manifest file listing the configured packages, their version, license and
+  related information.
+  Some of these information might be not defined in Buildroot; in this case
+  they are clearly marked as "unknown" or similar.
+* A +licenses/+ subdirectory, which contains the license text of packages.
+  If the license file(s) are not defined in Buildroot, the file is not produced
+  and a warning in the +README+ indicates this.
+
+Please note that the aim of the +legal-info+ feature of Buildroot is to
+produce all the material that is somehow relevant for legal compliance with the
+package licenses. Buildroot does not try to produce the exact material that
+you must somehow make public. It does surely produce some more material than is
+needed for a strict legal compliance. For example, it produces the source code
+for packages released under BSD-like licenses, that you might not want to
+redistribute in source form.
+
+Moreover, due to technical limitations, Buildroot does not produce some
+material that you will or may need, such as the toolchain source code and the
+Buildroot source code itself.
+When you run +make legal-info+, Buildroot produces warnings in the +README+
+file to inform you of relevant material that could not be saved.
+
+Here is a list of the licenses that are most widely used by packages in
+Buildroot, with the name used in the manifest file:
+
+* +GPLv2+:
+  http://www.gnu.org/licenses/old-licenses/gpl-2.0.html[
+  GNU General Public License, version 2];
+* +GPLv2++:
+  http://www.gnu.org/licenses/old-licenses/gpl-2.0.html[
+  GNU General Public License, version 2]
+  or (at your option) any later version;
+* +GPLv3+:
+  http://www.gnu.org/licenses/gpl.html[
+  GNU General Public License, version 3];
+* +GPLv3++:
+  http://www.gnu.org/licenses/gpl.html[
+  GNU General Public License, version 3]
+  or (at your option) any later version;
+* +GPL+:
+  http://www.gnu.org/licenses/gpl.html[
+  GNU General Public License] (any version);
+* +LGPLv2.1+:
+  http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html[
+  GNU Lesser General Public License, version 2.1];
+* +LGPLv2.1++:
+  http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html[
+  GNU Lesser General Public License, version 2.1]
+  or (at your option) any later version;
+* +LGPLv3+:
+  http://www.gnu.org/licenses/lgpl.html[
+  GNU Lesser General Public License, version 3];
+* +LGPLv3++:
+  http://www.gnu.org/licenses/lgpl.html[
+  GNU Lesser General Public License, version 3]
+  or (at your option) any later version;
+* +LGPL+:
+  http://www.gnu.org/licenses/lgpl.html[
+  GNU Lesser General Public License] (any version);
+* +BSD-4c+: Original BSD 4-clause license;
+* +BSD-3c+: BSD 3-clause license;
+* +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.
-- 
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 ` Luca Ceresoli [this message]
2012-05-17 17:33 ` [Buildroot] [PATCH v4 09/22] manual: add advice about GPL compliance for Buildroot Luca Ceresoli
2012-05-17 20:56   ` 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-9-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.