|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 'docs')
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/manual/legal-notice.txt b/docs/manual/legal-notice.txt
index a4911f7d4f..7c19bc30ab 100644
@@ -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