[OE-core] LICENSE_{X}-xxx is parsed?

[Flanagan, Elizabeth]

On Wed, Apr 25, 2012 at 1:17 AM, Richard Purdie
<richard.purdie at linuxfoundation.org> wrote:
> On Tue, 2012-04-24 at 16:13 -0700, Flanagan, Elizabeth wrote:
>> On Tue, Apr 24, 2012 at 3:53 PM, Chris Larson <clarson at kergoth.com> wrote:
>> > On Tue, Apr 24, 2012 at 3:38 PM, Flanagan, Elizabeth
>> > <elizabeth.flanagan at intel.com> wrote:
>> >> The rest of the packages in the bb should be inheriting LICENSE if no
>> >> PN level license is set. Which obviously causes problems for the above
>> >> example.
>> >>
>> >> In a case like above you'd want to do either of the following:
>> >>
>> >> a. Call out each package's license individually (better but can be
>> >> painful for recipes with lots of packages)
>> >> b. Leave GPLv3 out of LICENSE (easier but not technically accurate) so
>> >> undefined package level licensing inherits the correct LICENSE.
>> >
>> > I wonder if a partially specified set of individual package settings
>> > should be identified by some sanity check (an explicit, rather than
>> > implicit, one, like recipe_sanity) as a potential bug / source of
>> > confusion.
>>
>> It's something I've been thinking heavily about how over the past few
>> month. How to implement full package level license support without
>> requiring too many recipe changes. The current setup licensing moves
>> us in the right direction, without having to do too many recipe
>> changes, but there are some inadequacies in it and we may have to
>> address them sooner or later.
>
> I like the idea that LICENSE is the default and is used where no other
> LICENSE is set. If our LICENSE field building code is clever enough to
> be able to find any LICENSE_xxx variables that are set now, we could
> just define LICENSE to be the default LICENSE unless something else is
> set. It would then be up to the license handling code to create the xxx
> & xxx expressions where needed.
>
> This keeps things simpler for the recipes but still gets us where we
> need to be. I don't think forcing users to set LICENSE for every
> subpackage will be particularly useful, nor is having the top LICENSE
> field being a complete summary when we could calculate that.
>

I don't necessarily disagree, however, it is a change to how that
field has been historically used from my understanding. If people are
fine with using it that way, let's document it, let everyone know
about it and start looking at which recipes need to be updated to do
it correctly.

>> > I suspect most of the time it should be one or the other,
>> > either no individual package LICENSEs are defined, or they all should
>> > be.
>>
>> I would tend to agree. One thing I think we may want to start
>> considering (even if it does make me cringe a bit) is that if we go
>> this route, we may want to support LIC_SRC_URI_${PN} as well. It means
>> quite a few recipe changes, but it yet another step in more accurate
>> license auditing.
>
> Please, no ;-). Do something like the SRC_URI checksums (name the urls,
> then apply extra information to them, or use parameters in the urls.

Ahhh, yes. That's a much better idea. :)

-b

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



-- 
Elizabeth Flanagan
Yocto Project
Build and Release