[oe] [RFC] LICENSE fields and packages

[Koen Kooi]

On 25-11-08 21:13, Marcin Juszkiewicz wrote:
> Tuesday 25 of November 2008 20:26:24 Koen Kooi napisał(a):

>> Back to the point: what do you think of allowing URLs in the LICENSE
>> field?
>
> Show me code which will make use of it first? Why not add license to
> SRC_URI?

At this point it's not about code, it's about being able to show a legal 
department that the license is referenced in the package.

How would a non-OE user know that http://openembedded.org/dl/ICA2.txt is 
the license? Shipping the license itself in the packages would be 
better, but that will need a lot of thought, since we can't have a 1000 
packages shipping /usr/share/licenses/GPLv2, and *all* packages from a 
recipe need a license, even -doc, -dev -and -dbg.

The concrete problem I have is that I have a bunch of licenses that 
don't have a name (not even inside the company that wrote them), so my 
recipes have things like

LICENSE = "proprietary binary"
LICENSE = "evil binary"

So as short term solution I'd like to be able to point to a url for the 
'licenses without a proper name' and for the long term have a proper, 
package format independant solution.

regards,

Koen