From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] LICENSE fields and packages
Date: Wed, 26 Nov 2008 15:18:10 +0100 [thread overview]
Message-ID: <ggjlr3$j1i$1@ger.gmane.org> (raw)
In-Reply-To: <1227707875.15601.41.camel@mill.internal.reciva.com>
On 26-11-08 14:57, Phil Blundell wrote:
> On Wed, 2008-11-26 at 13:27 +0100, Koen Kooi wrote:
>> On 26-11-08 12:31, Phil Blundell wrote:
>>> On Wed, 2008-11-26 at 12:21 +0100, Koen Kooi wrote:
>>>>> ${PN}-license package on which all entries from PACKAGES will RDEPEND?
>>>> Any objections to doing it this way till we have a proper bbclass?
>>> I think this is a fine idea. It should be a DISTRO opt-in choice, of
>>> course, but I can't see any reason not to provide the facility.
>> My idea was to make it opt-in on a per package basis since DISTROs can
>> include base-files-doc for the most commit licenses (GPL, MIT, BSD, etc).
>
> Hm, right. I guess the selection should be both per-package and
> per-DISTRO.
>
> How about allowing the DISTRO to specify a regexp for the licences that
> it "knows about"; any package for which ${LICENSE} doesn't match the
> regexp will get the ${PN}-license thing. The default regexp would be
> set to ".*" in bitbake.conf, in order to preserve the current behaviour
> of not emitting any ${PN}-license; DISTROs that want to make use of the
> new feature can set it to whatever they like.
Sounds great.
regards,
Koen
prev parent reply other threads:[~2008-11-26 14:21 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
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 [this message]
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='ggjlr3$j1i$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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.