From: Bob Cochran <openembedded@mindchasers.com>
To: openembedded-devel@lists.openembedded.org
Cc: Peter Bigot <bigotp@acm.org>
Subject: Re: oe-core license description practices
Date: Sun, 20 May 2012 20:43:56 -0400 [thread overview]
Message-ID: <4FB98FCC.9050306@mindchasers.com> (raw)
In-Reply-To: <CAPOJ94OspH5H4G-=wQNqb=DdHratNwV3LHYnYo2BW43sbavk+g@mail.gmail.com>
On 01/15/2012 10:15 AM, Peter Bigot wrote:
> I need a resolution to this question so I can complete the port of an
> oe-classic recipe to oe-core.
>
> http://www.openembedded.org/wiki/OpenEmbedded-Core states that the
> LICENSE field should be "as correct as possible (e.g. 'GPLv2', not
> just 'GPL')". If the upstream package self-describes as "GPL", is it
> necessary that this be refined to a more specific version? I again
> note there are numerous existing recipes that do not provide more than
> "GPL".
>
> Depending on the answer, I will resubmit with a license of GPL | HPND
> or will attempt to contact the upstream maintainer for clarification.
>
> Thanks.
>
> Peter
>
> On Sat, Dec 31, 2011 at 3:28 PM, Peter Bigot<bigotp@acm.org> wrote:
>> On Sat, Dec 31, 2011 at 1:40 PM, Koen Kooi<koen@dominion.thruhere.net> wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
snip
Hi Peter,
Did this get resolved? I'm not finding python-mysqldb on the git server
outside of classic.
However, I did make use of the 1.2.3 patches you offered on 12/31/11, so
thanks for that. I have done some minimal testing with django tonight,
and it seems to be working OK.
Bob
next prev parent reply other threads:[~2012-05-21 1:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-15 15:15 oe-core license description practices Peter Bigot
2012-01-15 16:05 ` Chris Larson
2012-01-15 16:22 ` Peter Bigot
2012-01-15 16:52 ` Mark Hatle
2012-05-21 0:43 ` Bob Cochran [this message]
2012-05-21 10:51 ` Peter Bigot
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=4FB98FCC.9050306@mindchasers.com \
--to=openembedded@mindchasers.com \
--cc=bigotp@acm.org \
--cc=openembedded-devel@lists.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.