From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] LICENSE fields and packages
Date: Tue, 25 Nov 2008 22:02:00 +0100 [thread overview]
Message-ID: <gghp49$76g$1@ger.gmane.org> (raw)
In-Reply-To: <200811252113.50363.openembedded@haerwu.biz>
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
next prev parent reply other threads:[~2008-11-25 21:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 19:26 [RFC] LICENSE fields and packages Koen Kooi
2008-11-25 19:54 ` Richard Purdie
2008-11-25 20:40 ` Koen Kooi
2008-11-25 20:13 ` Marcin Juszkiewicz
2008-11-25 21:02 ` Koen Kooi [this message]
2008-11-25 21:42 ` Marcin Juszkiewicz
2008-11-25 21:57 ` Koen Kooi
2008-11-26 9:11 ` Marcin Juszkiewicz
2008-11-26 10:38 ` Koen Kooi
2008-11-26 11:21 ` Koen Kooi
2008-11-26 11:31 ` Phil Blundell
2008-11-26 12:27 ` Koen Kooi
2008-11-26 13:57 ` Phil Blundell
2008-11-26 14:18 ` Koen Kooi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='gghp49$76g$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox