From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libbsd: bump to version 0.9.1
Date: Wed, 6 Jun 2018 21:06:57 +0200 [thread overview]
Message-ID: <20180606190657.GB2537@scaer> (raw)
In-Reply-To: <20180606075802.3f397dd9@windsurf>
Thomas, Baruch, All,
On 2018-06-06 07:58 +0200, Thomas Petazzoni spake thusly:
> On Wed, 6 Jun 2018 07:01:31 +0300, Baruch Siach wrote:
[--SNIP--]
> > 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).
From https://libbsd.freedesktop.org/wiki/ :
"Most of the licenses are either ISC, MIT, Beerware, BSD-2-clause,
BSD-3-clause, and BSD-4-clause [...]"
So, we should probably at least list just those:
LIBBSD_LICENSE = ISC, MIT, Beerware, BSD-2-clause, BSD-3-clause, BSD-4-clause
My $0.02...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-06-06 19:06 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
2018-06-06 19:06 ` Yann E. MORIN [this message]
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=20180606190657.GB2537@scaer \
--to=yann.morin.1998@free.fr \
--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