All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: cleaning recipes
Date: Mon, 16 Aug 2010 18:32:23 +0200	[thread overview]
Message-ID: <i4bp6n$8cv$1@dough.gmane.org> (raw)
In-Reply-To: <20100816140055.GB7983@zlo.nu>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 16-08-10 16:00, Marc Olzheim wrote:
> On Mon, Aug 16, 2010 at 03:43:10PM +0200, Frans Meulenbroeks wrote:
>>> Hmm, the "guidelines" do not mention anything about licenses. Thus the
>>> only version you left of coreutils after
>>> 82dcd385984ba059b346a0e37fd3e14d536074ad is infected with GPLv3, while
>>> the older (6.0) GPLv2 version works fine for us.  I do not know
>>> whether other people mind about licenses, but we cannot use any GPLv3
>>> software in our image, because of its viral nature.
>>>
>>> Marc
>>
>> Valid point.
>> I did not consider licenses. Although the company I work for has no
>> problems with GPLv2, I understand your concern
>> What would be the most recent version of coreutils that is still using v2?
>> We can reinstate that one.
> 
> In the case of coreutils, that is 6.0.
> GPLv2 is ok here as well. The problem with GPLv3 here is that as soon as
> we incorporate some GPLv3 package we need to provide the abilitiy for
> customers to rebuild their image (Right to Tinker), which we cannot and
> will not do.

And the patent clause isn't fun if your company has tons of IP in that
area (like mine).

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMaWgWMkyGM64RGpERAg6PAJ4+ANeicD6Iwz5VOFF7FXwBNIdtXgCeMZKK
Ue6O0IThYTeDJ8RcCKbwIjE=
=Rn2H
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-08-16 16:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-15 14:59 cleaning recipes Frans Meulenbroeks
2010-08-15 15:15 ` Paul Menzel
2010-08-16  3:19 ` Mike Westerhof
2010-08-16  7:26   ` Frans Meulenbroeks
2010-08-16  4:25 ` Mike Westerhof
2010-08-16  6:15   ` Khem Raj
2010-08-16  7:39     ` Frans Meulenbroeks
2010-08-16  7:10   ` Robert Schuster
2010-08-16  8:58 ` Koen Kooi
2010-08-16  9:24   ` Frans Meulenbroeks
2010-08-16  9:30     ` Frans Meulenbroeks
2010-08-16 10:20       ` Koen Kooi
2010-08-16 11:10         ` Frans Meulenbroeks
2010-08-16 11:36           ` Koen Kooi
2010-08-16 12:14             ` Frans Meulenbroeks
2010-08-16 12:30               ` Graeme Gregory
2010-08-16 19:38                 ` Frans Meulenbroeks
2010-08-16 19:43                   ` Graeme Gregory
2010-08-16 13:23 ` Marc Olzheim
2010-08-16 13:43   ` Frans Meulenbroeks
2010-08-16 14:00     ` Marc Olzheim
2010-08-16 16:32       ` Koen Kooi [this message]
2010-08-16 19:09       ` Frans Meulenbroeks

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='i4bp6n$8cv$1@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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.