Skip to content

Commit

Permalink
docs: libtool patches are not handled by legal-info infrastructure.
Browse files Browse the repository at this point in the history
Signed-off-by: Romain Naour <[email protected]>
Cc: "Yann E. MORIN" <[email protected]>
Cc: Thomas Petazzoni <[email protected]>
Cc: Arnout Vandecappelle <[email protected]>
Reviewed-by: "Yann E. MORIN" <[email protected]>
[Thomas: slightly reword with Yann's suggestion.]
Signed-off-by: Thomas Petazzoni <[email protected]>
RomainNaour authored and tpetazzoni committed Aug 19, 2016
1 parent 561622e commit 9c6b9a2
Showing 2 changed files with 10 additions and 0 deletions.
5 changes: 5 additions & 0 deletions docs/manual/legal-notice.txt
Original file line number Diff line number Diff line change
@@ -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
5 changes: 5 additions & 0 deletions support/legal-info/README.header
Original file line number Diff line number Diff line change
@@ -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.

0 comments on commit 9c6b9a2

Please sign in to comment.