From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Sean Hudson <sean_hudson@mentor.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Recipes erroneously marked as "commercial"?
Date: Tue, 06 May 2014 21:54:53 +0100 [thread overview]
Message-ID: <1399409693.31891.5.camel@ted> (raw)
In-Reply-To: <536943C2.3040800@mentor.com>
On Tue, 2014-05-06 at 15:19 -0500, Sean Hudson wrote:
> On 05/06/2014 03:00 PM, Denys Dmytriyenko wrote:
> > So, long time ago we had a short list of "commercial" packages in a global
> > variable COMMERCIAL_LICENSE:
> >
> > COMMERCIAL_LICENSE ?= "lame gst-fluendo-mp3 libmad mpeg2dec ffmpeg qmmp"
> >
> > Then, at some point, the packages that depend on commercial ones were added to
> > the list, to allow wold builds to be successful:
> >
> > http://cgit.openembedded.org/openembedded-core/commit/?id=c69453fe94a649c518b0e6d79616f05579b864ce
> >
> > So, the list was appended with this:
> >
> > COMMERCIAL_LICENSE_DEPENDEES ?= "gst-plugins-ugly libomxil gst-openmax"
> >
> > Then, later on, the feature was changed from a global list to a per-recipe
> > flags:
> >
> > http://cgit.openembedded.org/openembedded-core/commit/?id=a2760661b8c7a4a1b6f2e556853b3a9ae38cbcb5
> > http://cgit.openembedded.org/openembedded-core/commit/?id=43410523a07d9eb52a7d57ae3dc1cc320cbbc6f9
> >
> > And all those recipes got marked with LICENSE_FLAGS = "commercial"
> > automatically, even if they are not really commercial.
> >
> > The question is - should we clean those up now? I can send a quick patch, if
> > my understanding above is correct.
> >
> I encountered this issue recently and raised it in IRC. As an
> interested party, I'd love to see these updated.
>
> (Thanks Denys for sending it to the list so quickly.)
If world builds don't break I'm open to patches.
Cheers,
Richard
prev parent reply other threads:[~2014-05-06 20:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 20:00 Recipes erroneously marked as "commercial"? Denys Dmytriyenko
2014-05-06 20:19 ` Sean Hudson
2014-05-06 20:54 ` Richard Purdie [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=1399409693.31891.5.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=sean_hudson@mentor.com \
/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.