License attributions for a system built with OpenEmbedded.

License attributions for a system built with OpenEmbedded.

[Tasslehoff Kjappfot]

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?

- Tasslehoff

Re: License attributions for a system built with OpenEmbedded.

[Khem Raj]

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 :)


>
> - Tasslehoff
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: License attributions for a system built with OpenEmbedded.

[Tasslehoff Kjappfot]

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

Re: License attributions for a system built with OpenEmbedded.

[Paul Eggleton]

On Tuesday 15 May 2012 13:35:24 Tasslehoff Kjappfot wrote:
> 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.

[Disclaimer: I'm not a lawyer, this is not legal advice, etc.]

Ultimately you have to comply with the terms set out in the licenses of the 
code you're distributing. For example, if those licenses require you to 
provide the source code (or a written offer for same) regardless of whether you 
have changed the source or not, then that's what you have to do for the 
software you distribute under that license.

At the very least you should check all of the licenses to make sure you 
understand your obligations.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre