From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libbsd: bump to version 0.9.1
Date: Wed, 6 Jun 2018 07:58:02 +0200 [thread overview]
Message-ID: <20180606075802.3f397dd9@windsurf> (raw)
In-Reply-To: <20180606040131.drvicwte22lzicad@sapphire.tkos.co.il>
Hello,
On Wed, 6 Jun 2018 07:01:31 +0300, Baruch Siach wrote:
> > because the license text itself refers to Peter Wemm.
>
> The libbsd COPYING fine appends the copyright holder to a number of common
> licenses like BSD-3-clause-John-Birrell and BSD-4-clause-Niels-Provos. That's
> probably because each COPYING entry lists specific files with their copyright
> holders.
Correct.
> We usually only use the SPDX identifier string. So I don't think
> there is a reason to do that for this license.
Well, normally an SPDX identifier string refers to a specific version
of the license. If the license text is different (even for subtle
reasons), the SPDX identifier string should probably be different.
> > Yocto is really using a longer list of licenses:
> > https://git.yoctoproject.org/cgit.cgi/poky/plain/meta/recipes-support/libbsd/libbsd_0.8.7.bb
>
> The full list is only in a comment, AFAICS.
True, indeed, I had missed that.
> The actual effective line is
> rather shorter than what we have following this patch:
>
> LICENSE = "BSD-4-Clause & ISC & PD"
I also think it is good enough. But I wanted to point out that the
licensing is in fact a bit more complicated. I personally don't see the
need of having a more detailed LIBBSD_LICENSE description, but I wanted
to point this out so that others can comment on this (Arnout, Yann,
Peter).
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-06-06 5:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 18:19 [Buildroot] [PATCH] libbsd: bump to version 0.9.1 Baruch Siach
2018-06-05 20:16 ` Thomas Petazzoni
2018-06-06 4:01 ` Baruch Siach
2018-06-06 5:58 ` Thomas Petazzoni [this message]
2018-06-06 19:06 ` Yann E. MORIN
2018-06-07 18:55 ` Arnout Vandecappelle
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=20180606075802.3f397dd9@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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