From: Matthias Hentges <oe@hentges.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Removal of GPL recipes
Date: Sat, 14 Apr 2007 16:11:52 +0200 [thread overview]
Message-ID: <1176559912.7958.5.camel@localhost.localdomain> (raw)
In-Reply-To: <3ef3a7ad0704140545j18e0ce1aib8a707966b74f313@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 623 bytes --]
Am Samstag, den 14.04.2007, 13:45 +0100 schrieb José Bernardo Bandos
Rodrigues:
> I'm not sure I get this one - you're proposing to remove those recipes
> because they are GPL licensed?
There is some sort of policy that all OE recieped must be MIT licensed
(to ease corporate usage IIRC). But this policy of course only covers
the .bb file itself, not any software built with it.
--
Matthias 'CoreDump' Hentges
Cologne / Germany
Webmaster of Hentges.net & Embedded Linux Developer
GPG -> gpg --keyserver gpg-keyserver.de --recv-keys 0xAF3030D9
My OS: Debian SID: Geek by Nature, Linux by Choice
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 196 bytes --]
prev parent reply other threads:[~2007-04-14 14:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-13 21:48 [RFC] Removal of GPL recipes Holger Freyther
2007-04-14 9:58 ` Matthias Hentges
2007-04-14 12:45 ` José Bernardo Bandos Rodrigues
2007-04-14 14:11 ` Matthias Hentges [this message]
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=1176559912.7958.5.camel@localhost.localdomain \
--to=oe@hentges.net \
--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.