From: Tomas Frydrych <tf+lists.yocto@r-finger.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/4] pulseaudio: add GConf dependency
Date: Tue, 30 Oct 2012 10:44:10 +0000 [thread overview]
Message-ID: <508FAF7A.2070706@r-finger.com> (raw)
In-Reply-To: <CAK18fxFcMPNVPXy6QcFAKAUmgyF83fBAX_BdUS8nLG=f=KQgyw@mail.gmail.com>
On 30/10/12 10:31, Andrei Gherzan wrote:
>> gnome-common is some scripts and tools used at configure time, so
>> there isn't any linkage, so there isn't any GPLv3 in the images, so
>> there isn't a problem.
>>
>> The question is how do we express this?
>>
>>
> Should it be whitelisted?
The problem with whitelisting is that if the usage changes from the
assumptions the whitelisting was originally made on, this will not
automatically remove the whitelisting -- if whitlisting is the solution
here, it needs to be left to the Yocto users to do it locally based on
their own review of the situation.
I think to handle this scenario properly, you would need two sets of
license controls, one for 'build tools' and one for 'things that ship'.
Tomas
next prev parent reply other threads:[~2012-10-30 10:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 16:37 [PATCH 1/4] pulseaudio: add GConf dependency Ross Burton
2012-10-24 16:37 ` [PATCH 2/4] pulseaudio: move helper binaries into the relevant module packages Ross Burton
2012-10-24 16:37 ` [PATCH 3/4] pulseaudio: fix library packaging Ross Burton
2012-10-24 16:37 ` [PATCH 4/4] pulseaudio: remove libpulse-browse, removed upstream in 2011 Ross Burton
2012-10-24 18:09 ` [PATCH 1/4] pulseaudio: add GConf dependency Martin Jansa
2012-10-24 19:30 ` Burton, Ross
2012-10-28 1:17 ` Saul Wold
2012-10-30 9:59 ` Andrei Gherzan
2012-10-30 10:02 ` Burton, Ross
2012-10-30 10:10 ` Andrei Gherzan
2012-10-30 10:19 ` Burton, Ross
2012-10-30 10:31 ` Andrei Gherzan
2012-10-30 10:44 ` Tomas Frydrych [this message]
2012-10-30 11:00 ` Burton, Ross
2012-10-30 16:06 ` Koen Kooi
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=508FAF7A.2070706@r-finger.com \
--to=tf+lists.yocto@r-finger.com \
--cc=openembedded-core@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.