[Buildroot] [PATCH RFC] legal-info: add option to store manifest in rootfs

Thomas Petazzoni thomas.petazzoni at bootlin.com
Sat Apr 28 10:20:04 UTC 2018


Hello,

On Fri, 27 Apr 2018 14:39:20 -0700, Florian Fainelli wrote:

> > Well, sure, it makes some sense _practically_, but not _legally_ AFAICU,
> > because to be compliant you still would need a written license statement
> > (e.g. in the printed user manual).
> > 
> > Do we want to support every way that makes sense? We have two at least:
> > store the manifest and store manifest + license text. If we want to
> > support both, maybe that would actually carry more complexity than
> > usefulness, I'm afraid.
> > 
> > But of course I might be partially wrong! :-]  
> 
> Let's drop this, I was not thinking this would go into such a lengthy
> discussion, I will keep the local hack I have with make legal-info in
> post-build.sh. Thanks a lot for your help Yann!

Well, could you share some details about your specific use-case ? As
explained by Luca, having just the list of software components and the
name of their license isn't enough, the complete license text is needed
for licence compliance.

Knowing this, what is the use-case for having just the manifest ?

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com



More information about the buildroot mailing list