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

[Florian Fainelli <f.fainelli@gmail.com>]

On 04/28/2018 03:20 AM, Thomas Petazzoni wrote:
> 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 ?

The use case is to have an UI page which is able to list the different
packages included, their version, a link to their license as well as
their sources. This is by no means meant to be a lawyer proof license
compliance page, just something that can eventually be used as a
template to reach that goal.

You and others have convinced me into keeping this a local modification,
I see no point in continuing this discussion any further given it was
asked as seemingly naive question.
-- 
Florian