[Buildroot] [PATCH v2 3/3] docs: libtool patches are not handled by legal-info infrastructure.

Romain Naour romain.naour at gmail.com
Wed Aug 17 16:01:10 UTC 2016


Signed-off-by: Romain Naour <romain.naour at gmail.com>
Cc: "Yann E. MORIN" <yann.morin.1998 at free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>
Cc: Arnout Vandecappelle <arnout at mind.be>
---
 docs/manual/legal-notice.txt     | 4 ++++
 support/legal-info/README.header | 4 ++++
 2 files changed, 8 insertions(+)

diff --git a/docs/manual/legal-notice.txt b/docs/manual/legal-notice.txt
index a4911f7..fd1e5aa 100644
--- a/docs/manual/legal-notice.txt
+++ b/docs/manual/legal-notice.txt
@@ -44,6 +44,10 @@ There you will find:
   Patches that were applied are also saved, along with a file named +series+
   that lists the patches in the order they were applied. Patches are under the
   same license as the files that they modify.
+  Note: Buildroot applies additional patches to Libtool scripts of
+  autotools-based packages. These patches can be found under +support/libtool+
+  in the buildroot source and are not saved with the package sources due to
+  technical limitations. You may need to collect them manually.
 * 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
diff --git a/support/legal-info/README.header b/support/legal-info/README.header
index 1f3524f..ee34886 100644
--- a/support/legal-info/README.header
+++ b/support/legal-info/README.header
@@ -20,6 +20,10 @@ This material is composed of the following items.
    with a file named 'series' that lists the patches in the order they were
    applied. Patches are under the same license as the files that they modify
    in the original package.
+   Note: Buildroot applies additional patches to Libtool scripts of
+   autotools-based packages. These patches can be found under support/libtool
+   in the buildroot source and are not saved with the package sources due to
+   technical limitations. You may need to collect them manually.
  * A manifest file listing the configured packages and related information.
  * The license text of the packages; they have been saved in the licenses/
    subdirectory.
-- 
2.5.5



More information about the buildroot mailing list