Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas De Schampheleire <patrickdepinguin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 6 of 6 v2] legal info: update documentation with split target/host output
Date: Mon, 07 Oct 2013 15:15:13 +0200	[thread overview]
Message-ID: <80513bfceb0f901ca09a.1381151713@argentina> (raw)
In-Reply-To: <patchbomb.1381151707@argentina>

Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>

---
v2: new patch

 docs/manual/legal-notice.txt |  15 +++++++++------
 1 files changed, 9 insertions(+), 6 deletions(-)

diff --git a/docs/manual/legal-notice.txt b/docs/manual/legal-notice.txt
--- a/docs/manual/legal-notice.txt
+++ b/docs/manual/legal-notice.txt
@@ -39,16 +39,19 @@ There you will find:
 * +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.
+* The source code for all packages; this is saved in the +sources/+ and
+  +host-sources/+ subdirectories for target and host packages respectively.
+  The source code for packages that set +<PKG>_REDISTRIBUTE = NO+ will not be
+  saved.
+  Patches applied to some packages by Buildroot are distributed with the
+  Buildroot sources and are not duplicated in the +sources/+ and +host-sources/+
+  subdirectories.
+* A manifest file (one for host and one for target packages) listing the
+  configured packages, their version, license and related information.
   Some of this information might not be defined in Buildroot; such items are
   marked as "unknown".
-* A +licenses/+ subdirectory, which contains the license text of packages.
+* The license texts of all packages, in the +licenses/+ and +host-licenses/+
+  subdirectories for target and host packages respectively.
   If the license file(s) are not defined in Buildroot, the file is not produced
   and a warning in the +README+ indicates this.
 
@@ -72,7 +75,7 @@ License abbreviations
 ---------------------
 
 Here is a list of the licenses that are most widely used by packages in
-Buildroot, with the name used in the manifest file:
+Buildroot, with the name used in the manifest files:
 
 * `GPLv2`:
   http://www.gnu.org/licenses/old-licenses/gpl-2.0.html[

  parent reply	other threads:[~2013-10-07 13:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-07 13:15 [Buildroot] [PATCH 0 of 6 v2] legal info: split host and package output Thomas De Schampheleire
2013-10-07 13:15 ` [Buildroot] [PATCH 1 of 6 v2] legal info: fix saving of host package licenses Thomas De Schampheleire
2013-11-11 11:56   ` Thomas De Schampheleire
2013-11-11 22:49   ` Luca Ceresoli
2013-11-12  7:12   ` Arnout Vandecappelle
2013-11-12  8:25     ` Thomas De Schampheleire
2013-10-07 13:15 ` [Buildroot] [PATCH 2 of 6 v2] legal info: split manifest for host and target Thomas De Schampheleire
2013-10-07 13:15 ` [Buildroot] [PATCH 3 of 6 v2] legal info: split license texts " Thomas De Schampheleire
2013-10-07 13:15 ` [Buildroot] [PATCH 4 of 6 v2] legal info: split sources " Thomas De Schampheleire
2013-10-07 13:15 ` [Buildroot] [PATCH 5 of 6 v2] legal info: cleanup utility functions Thomas De Schampheleire
2013-10-07 13:15 ` Thomas De Schampheleire [this message]
2013-11-11 11:57   ` [Buildroot] [PATCH 6 of 6 v2] legal info: update documentation with split target/host output Thomas De Schampheleire
2013-11-11 21:35     ` Samuel Martin

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=80513bfceb0f901ca09a.1381151713@argentina \
    --to=patrickdepinguin@gmail.com \
    --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