All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libgit2: Bump to version 1.0.0
Date: Wed, 15 Apr 2020 23:16:36 +0200	[thread overview]
Message-ID: <20200415211636.GJ5853@scaer> (raw)
In-Reply-To: <20200415223258.2d5d406c@windsurf.home>

Thomas, All,

On 2020-04-15 22:32 +0200, Thomas Petazzoni spake thusly:
> On Tue, 14 Apr 2020 11:14:39 +0200
> Nicolas Cavallari <nicolas.cavallari@green-communications.fr> wrote:
[--SNIP--]
> > +LIBGIT2_LICENSE = GPL-2.0 with linking exception, BSD 4-clause variant (wildmatch), MIT (sha1)
> But here is the part that made me not apply the patch: this BSD
> 4-clause variant thing. The license text is at
> https://github.com/libgit2/libgit2/blob/master/COPYING#L995 and it
> doesn't seem to be a license known at https://spdx.org/licenses/. I'm
> not sure how to properly encode it.
> 
> Yann, Arnout, any suggestion?

We should only encode known, exact matches. Otherwise, we should only
list it like we do unknown license, like:

    libgit2 license (wildmatch)

What does not help in fact, is that the code does not originate
libgit2, but from git, which itself got it from rsync before it turned
GPLv3, which got it from somewhere.

However, the code is credited to a certain Rich Salz, in 1986, 34 years
ago now. There is even a Wikipedia page [0] about something really
closely related, wildmat, which is also described as bsing a pattern
matching library writen in 1986 by said Rich Salz. There is a wildmat
on github [1], also posted by Rich Salz, where they dedicate it to the
public domain.

[0] https://en.wikipedia.org/wiki/Wildmat
[1] https://github.com/richsalz/wildmat

Still, that does not say much about the actual copy in libgit2...

So, I'd just say something like

    wildmatch license (wildmatch)

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

      reply	other threads:[~2020-04-15 21:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-14  9:14 [Buildroot] [PATCH 1/1] package/libgit2: Bump to version 1.0.0 Nicolas Cavallari
2020-04-15 20:32 ` Thomas Petazzoni
2020-04-15 21:16   ` Yann E. MORIN [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=20200415211636.GJ5853@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 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.