From 9c6b9a2bb0d74bf588a275dd14c0f373f302a5d2 Mon Sep 17 00:00:00 2001 From: Romain Naour Date: Wed, 17 Aug 2016 18:01:10 +0200 Subject: [PATCH] docs: libtool patches are not handled by legal-info infrastructure. Signed-off-by: Romain Naour Cc: "Yann E. MORIN" Cc: Thomas Petazzoni Cc: Arnout Vandecappelle Reviewed-by: "Yann E. MORIN" [Thomas: slightly reword with Yann's suggestion.] Signed-off-by: Thomas Petazzoni --- docs/manual/legal-notice.txt | 5 +++++ support/legal-info/README.header | 5 +++++ 2 files changed, 10 insertions(+) diff --git a/docs/manual/legal-notice.txt b/docs/manual/legal-notice.txt index a4911f7d4f..7c19bc30ab 100644 --- 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 1f3524f599..d3bdf71bcf 100644 --- 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. -- 2.30.2