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. p. _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
