All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Schmidt <stefan@datenfreihafen.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OpenEmbedded and the Yocto Project
Date: Sat, 6 Nov 2010 18:44:53 +0100	[thread overview]
Message-ID: <20101106174453.GN6691@excalibur.local> (raw)
In-Reply-To: <AANLkTi=9baSJYxwULah-FNS50gaK9bhF=aBG-4-ChrrP@mail.gmail.com>

Hello.

On Sat, 2010-11-06 at 13:26, Cliff Brake wrote:
> On Fri, Nov 5, 2010 at 12:07 PM, Richard Purdie <rpurdie@rpsys.net> wrote:
> 
> > So what do I mean by hard? First there are the conversations with your
> > legal department where some questions arise:
> >
> > * How do you ensure license compliance?
> > * When someone makes a change, how do you know the license is still
> >  correct?
> > * You've mixing GPLv2 and v3? How are you ensuring no contamination?
> > <cue a long discussion which I'd bet most companies have>
> 
> Is GPLv3 the issue here with patent, DMC, and Tivoization issues?  Is
> the solution to simply not have GPLv3 software in a device?

At least that is what I hear most of the times. Yocto should be able to build a
GPLv3-free image. Obviously this kinda results in keeping old versions of core
elements of software maintained by the FSF.

> Are there other license issues that companies are worried about?

Well, we have Google who demostrated that they would rather write everything
from scratch, including a libc, instead of using the GPL. :)

But that is not a problem for OE. All other players have realized how to deal
with the GPL.

regards
Stefan Schmidt



  reply	other threads:[~2010-11-06 17:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-05 16:07 OpenEmbedded and the Yocto Project Richard Purdie
2010-11-05 16:36 ` Paul Menzel
2010-11-05 19:24   ` Richard Purdie
2010-11-05 20:45     ` Frans Meulenbroeks
2010-11-05 16:37 ` Chris Larson
2010-11-06 17:26 ` Cliff Brake
2010-11-06 17:44   ` Stefan Schmidt [this message]
2010-11-06 21:01   ` Philip Balister
2010-11-07  7:26     ` Tian, Kevin
  -- strict thread matches above, loose matches on Subject: below --
2010-11-02 14:16 Philip Balister
2010-11-02 14:42 ` Koen Kooi
2010-11-02 19:55   ` Scott Garman
2010-11-02 22:00     ` Leon Woestenberg
2010-11-02 22:11       ` Scott Garman
2010-11-02 22:24   ` Richard Purdie
2010-11-02 22:44     ` Khem Raj
2010-11-03  9:09     ` Petr Štetiar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101106174453.GN6691@excalibur.local \
    --to=stefan@datenfreihafen.org \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.