|author||Romain Naour <firstname.lastname@example.org>||2016-08-17 18:01:10 +0200|
|committer||Thomas Petazzoni <email@example.com>||2016-08-19 23:16:23 +0200|
docs: libtool patches are not handled by legal-info infrastructure.
Signed-off-by: Romain Naour <firstname.lastname@example.org> Cc: "Yann E. MORIN" <email@example.com> Cc: Thomas Petazzoni <firstname.lastname@example.org> Cc: Arnout Vandecappelle <email@example.com> Reviewed-by: "Yann E. MORIN" <firstname.lastname@example.org> [Thomas: slightly reword with Yann's suggestion.] Signed-off-by: Thomas Petazzoni <email@example.com>
Diffstat (limited to 'support')
1 files changed, 5 insertions, 0 deletions
diff --git a/support/legal-info/README.header b/support/legal-info/README.header
index 1f3524f599..d3bdf71bcf 100644
@@ -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/