From: "André Draszik" <git@andred.net>
To: akuster808 <akuster808@gmail.com>,
openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH 1/2] uthash: update to v2.0.2
Date: Wed, 17 Jan 2018 09:58:07 +0000 [thread overview]
Message-ID: <1516183087.28972.69.camel@andred.net> (raw)
In-Reply-To: <fcae9a6d-a41f-b22a-7d10-b84bf02bd056@gmail.com>
On Tue, 2018-01-16 at 22:20 -0800, akuster808 wrote:
>
> On 01/12/2018 04:33 AM, André Draszik wrote:
> > On Fri, 2018-01-12 at 12:29 +0000, André Draszik wrote:
> > [...]
> > > +HOMEPAGE = "https://troydhanson.github.io/uthash/"
> > > +SECTION = "base"
> > > +LICENSE = "BSD-1-Clause"
> > > +LIC_FILES_CHKSUM =
> > > "file://LICENSE;md5=5cc1f1e4c71f19f580458586756c02b4"
> >
> > Note that there is no common license file for BSD-1-Clause in OE-core,
> > which
> > causes this warning:
> >
> > WARNING: <image> do_rootfs: The license listed BSD-1-Clause was not in
> > the licenses collected for recipe uthash
> >
> > Is this really the first recipe using BSD-1-Clause?
>
> Does the standalone "BSD" license over Clause 1?
Well, the stand-alone BSD license is effectively BSD-3-Clause, so it's of
course more restrictive than the 1-Clause version.
Cheers,
Andre'
prev parent reply other threads:[~2018-01-17 9:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 12:29 [meta-oe][PATCH 1/2] uthash: update to v2.0.2 André Draszik
2018-01-12 12:29 ` [meta-oe][PATCH 2/2] uthash: add ptest support André Draszik
2018-01-12 12:33 ` [meta-oe][PATCH 1/2] uthash: update to v2.0.2 André Draszik
2018-01-17 6:20 ` akuster808
2018-01-17 9:58 ` André Draszik [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=1516183087.28972.69.camel@andred.net \
--to=git@andred.net \
--cc=akuster808@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox