Re: License attributions for a system built with OpenEmbedded.

[Tasslehoff Kjappfot <tasskjapp@gmail.com>]

On 05/14/2012 11:24 PM, Khem Raj wrote:
> On Mon, May 14, 2012 at 5:02 AM, Tasslehoff Kjappfot
> <tasskjapp@gmail.com>  wrote:
>> Hi.
>>
>> I have made a rootfs and an SDK with OE-classic. We use the SDK to
>> compile our own application, which links dynamically with some open
>> source libraries.
>>
>> I have listed the LGPL libraries our application uses and linked to
>> http://www.gnu.org/licenses/lgpl.txt, but I don't know how/if to
>> attribute OpenEmbedded. Should I include attributions for every single
>> open source software in the rootfs+SDK, or is it sufficient to say that
>> I have compiled them using OpenEmbedded?
> most part of OE metadata are MIT licensed some parts may be GPL
>
> well while booting you could use OE splash screen instead of your company one :)
I'll see what I can do :)

I've already written that I use OpenEmbedded as a build system, and 
included the MIT license. I also used create_manifest.sh from Arago to 
get a list of everything included in the rootfs. What I really wonder is 
if I must add all that information as well.

I hereby guarantee that I won't take any answers as legal binding advice ;)

- Tasslehoff