[OE-core] [PATCH 2/5] Add LICENSE_FLAGS to packages mentioned in COMMERCIAL_LICENSE

[Tom Zanussi]

On Fri, 2012-01-06 at 19:20 +0000, Phil Blundell wrote:
> On Fri, 2012-01-06 at 12:03 -0600, Tom Zanussi wrote:
> > On Fri, 2012-01-06 at 17:15 +0000, Phil Blundell wrote:
> > > If I'm understanding the mechanism correctly then just setting all of
> > > these to "Commercial" seems like a bit of a retrograde step.  Is there
> > > an easy way in this new world for me to say that (for the sake of
> > > argument) gst-fluendo-mp3 is acceptable for inclusion but libomixl
> > > isn't?
> > > 
> > 
> > Hmm, I don't think it's retrograde - it's true, this patchset simply
> > replaces the existing functionality, where those particular packages
> > previously were all essentially marked "COMMERCIAL" by virtue of all
> > existing within the one-and-all COMMERCIAL_LICENSE variable, whereas now
> > they're all marked as "Commercial" instead.
> 
> Well, the sense in which it seems retrograde to me is that, previously,
> COMMERCIAL_LICENSE named a list of packages and I could add or remove
> things as I saw fit depending on my distro policy requirements.  Now,
> they're all just marked "Commercial" in an undifferentiated way and
> there doesn't seem to be any easy mechanism for me to take some but not
> all of them.
> 

Yeah, the global COMMERCIAL_LICENSE is convenient in that there's one
place you can go to see a list of affected packages, but it's kind of at
odds with allowing per-recipe flexibility for layers to add their own
license terms.

To accomplish the same thing as COMMERCIAL_LICENSE with LICENSE_FLAGS,
we could simply have each of the packages now listed in
COMMERCIAL_LICENSE define LICENSE_FLAGS = "Commercial_${PN}".

The downside is that to enable only the ones you want, you'd have to
know which are the ones you want in order to name them, which I guess
you should anyway (rather then have them all in convenient list to
remind you).  For convenience and to sort of address that problem for
the packages in oe-core, we could add a commented-out
LICENSE_FLAGS_WHITELIST containing all the currently-listed packages in
COMMERCIAL_LICENSE to the default local.conf.  Users of other layers
would have to know which additional packages to put in the whitelist,
but again, shouldn't they be conscious of that anyway?

Tom

> p.
> 
> 
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core