[oe] [PATCHv2] recipe licenses: update recipe LICENSE fields

[Andreas Oberritter]

On 10/20/2010 08:25 PM, Denys Dmytriyenko wrote:
> In OE we've been using this term for some time now. Although, still too many 
> old recipes use old notations, sometimes even as generic as just plain "GPL" 
> w/o specifying the exact version. It wasn't as critical before, but these days 
> OE is being adopted in corporate environments and proper licensing became 
> quite important.

How exactly do "GPLv2" and "GPLv2+" differ from a corporate point of
view? Can you imagine any company forking a GPLv2+-licensed project to
distribute it under the terms of a later version of the license?

Is there any case where someone would say "Hey, we can't use this
package, because it's GPLv2. We need it to be v3 or later"? The opposite
seems to be a common case instead.

I'm asking, because I don't think it's worth the time to verify all
packages in such detail, i.e. looking at all source files and guessing
what the original author intended to choose, if there are files called
COPYING or LICENSE in the root folder of a package.

The only case where it's important whether v2 or v2+ is in use is if you
want to stop using v2. IMO, if someone wants to do that, he should do
the research himself. It isn't important for a distribution.

Regards,
Andreas