docs: libtool patches are not handled by legal-info infrastructure.

Signed-off-by: Romain Naour <romain.naour@gmail.com>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Arnout Vandecappelle <arnout@mind.be>
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
[Thomas: slightly reword with Yann's suggestion.]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>

diff --git a/docs/manual/legal-notice.txt b/docs/manual/legal-notice.txt
index a4911f7d4fd6a7a241500bbbc5c07a5e0f180cc8..7c19bc30ab3386a8d138f2d467dbad38e58ac5e2 100644 (file)
--- a/docs/manual/legal-notice.txt
+++ b/docs/manual/legal-notice.txt
@@ -44,6 +44,11 @@ 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, due to technical
+  limitations, are not saved with the package sources. 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 1f3524f599491a97f705ef76e425f9aeaff3d7b4..d3bdf71bcffed012f5fdcd0197a3c7745f37398b 100644 (file)
--- a/support/legal-info/README.header
+++ b/support/legal-info/README.header
@@ -20,6 +20,11 @@ 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, due to technical
+   limitations, are not saved with the package sources. 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.