|author||Yann E. MORIN <firstname.lastname@example.org>||2016-10-01 17:26:32 +0200|
|committer||Thomas Petazzoni <email@example.com>||2016-10-03 23:19:07 +0200|
docs/manual: no warranty on output of legal-info
Explicitly state that there is no warranty about the accuracy of the content of the output of 'make legal-info'. Signed-off-by: "Yann E. MORIN" <firstname.lastname@example.org> Cc: Arnout Vandecappelle <email@example.com> Cc: Luca Ceresoli <firstname.lastname@example.org> Acked-by: Arnout Vandecappelle (Essensium/Mind) <email@example.com> Acked-by: Luca Ceresoli <firstname.lastname@example.org> Signed-off-by: Thomas Petazzoni <email@example.com>
Diffstat (limited to 'docs')
1 files changed, 10 insertions, 0 deletions
diff --git a/docs/manual/legal-notice.txt b/docs/manual/legal-notice.txt
index 7c19bc30ab..c9b5211f8d 100644
@@ -73,6 +73,16 @@ distribution is required).
When you run +make legal-info+, Buildroot produces warnings in the +README+
file to inform you of relevant material that could not be saved.
+Finally, keep in mind that the output of +make legal-info+ is based on
+declarative statements in each of the packages recipes. The Buildroot
+developers try to do their best to keep those declarative statements as
+accurate as possible, to the best of their knowledge. However, it is very
+well possible that those declarative statements are not all fully accurate
+nor exhaustive. You (or your legal department) _have_ to check the output
+of +make legal-info+ before using it as your own compliance delivery. See
+the _NO WARRANTY_ clauses (clauses 11 and 12) in the +COPYING+ file at the
+root of the Buildroot distribution.
=== License abbreviations