Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 13/16] erlang-jiffy: New package
Date: Wed, 31 May 2017 11:19:36 +0200	[thread overview]
Message-ID: <20170531111936.79596357@free-electrons.com> (raw)
In-Reply-To: <CAJtjsKa9mRtHaLjXcdbAi7w7_R=KNE3M_QSP-_SA=S=dGhqf1A@mail.gmail.com>

Hello,

On Wed, 31 May 2017 11:05:03 +0200, Johan Oudinet wrote:

> > Missing addition to the DEVELOPERS file. Please fix this in the 3
> > patches adding the 3 new packages.
> >  
> >> +ERLANG_JIFFY_VERSION = 0.14.8
> >> +ERLANG_JIFFY_SITE = $(call github,davisp,jiffy,$(ERLANG_JIFFY_VERSION))
> >> +ERLANG_JIFFY_LICENSE = MIT  
> >
> > There are some parts under BSD-3c, and tests under yet another license.
> > This should be indicated here.  
> 
> Yep, the licensing of this package is a real mess. I'm not very
> competent in this stuff. What should I put in addition to MIT and
> BSD-3c?
> I didn't understand the "Google double-conversion" reference in the
> LICENSE file and the commit that introduces it does not give more
> explanations.

I guess something like:

ERLANG_JIFFY_LICENSE = MIT (core), BSD-3-Clause (Google double conversion library), BSD-3-Clause (tests)

is good enough.

> That's an error. Thanks for spotting it. I'm not using the features
> offered by this package in my ejabberd configuration, that's why I
> haven't seen this bug.

Wait. Does this means that Jiffy is not a mandatory dependency to build
ejabberd? If that's the case, then ejabberd should not select it.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-05-31  9:19 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-30 14:51 [Buildroot] [PATCH 00/16] Bump ejabberd version to 17.04 Johan Oudinet
2017-05-30 14:51 ` [Buildroot] [PATCH 01/16] erlang-goldrush: bump version to 0.1.9 Johan Oudinet
2017-05-30 14:51 ` [Buildroot] [PATCH 02/16] erlang-lager: bump to version 3.2.1 Johan Oudinet
2017-05-30 14:51 ` [Buildroot] [PATCH 03/16] erlang-p1-utils: bump to version 1.0.8 Johan Oudinet
2017-05-30 14:51 ` [Buildroot] [PATCH 04/16] erlang-p1-zlib: bump to version 1.0.2 Johan Oudinet
2017-05-30 14:52 ` [Buildroot] [PATCH 05/16] erlang-p1-cache-tab: bump to version 1.0.7 Johan Oudinet
2017-05-30 14:52 ` [Buildroot] [PATCH 06/16] erlang-p1-iconv: bump to version 1.0.4 Johan Oudinet
2017-05-30 22:05   ` Thomas Petazzoni
2017-05-30 14:52 ` [Buildroot] [PATCH 07/16] erlang-p1-stringprep: bump to version 1.0.8 Johan Oudinet
2017-05-30 14:52 ` [Buildroot] [PATCH 08/16] erlang-p1-tls: bump to version 1.0.11 Johan Oudinet
2017-05-30 14:52 ` [Buildroot] [PATCH 09/16] erlang-p1-stun: bump to version 1.0.10 Johan Oudinet
2017-05-30 14:52 ` [Buildroot] [PATCH 10/16] erlang-p1-sip: bump to version 1.0.11 Johan Oudinet
2017-05-30 14:52 ` [Buildroot] [PATCH 11/16] erlang-p1-xml: bump to version 1.1.22 Johan Oudinet
2017-05-30 22:06   ` Thomas Petazzoni
2017-05-30 14:52 ` [Buildroot] [PATCH 12/16] erlang-p1-yaml: bump to version 1.0.9 Johan Oudinet
2017-05-30 14:52 ` [Buildroot] [PATCH 13/16] erlang-jiffy: New package Johan Oudinet
2017-05-30 22:07   ` Thomas Petazzoni
2017-05-31  9:05     ` Johan Oudinet
2017-05-31  9:19       ` Thomas Petazzoni [this message]
2017-05-31 11:42         ` Johan Oudinet
2017-05-30 14:52 ` [Buildroot] [PATCH 14/16] erlang-p1-oauth: " Johan Oudinet
2017-05-30 22:08   ` Thomas Petazzoni
     [not found]     ` <20170530230314.GN2009@localhost>
2017-05-31  7:28       ` Thomas Petazzoni
2017-05-30 14:52 ` [Buildroot] [PATCH 15/16] erlang-p1-xmpp: " Johan Oudinet
2017-05-30 22:08   ` Thomas Petazzoni
2017-05-30 14:52 ` [Buildroot] [PATCH 16/16] ejabberd: bump to version 17.04 Johan Oudinet
2017-05-30 22:10   ` Thomas Petazzoni
2017-05-30 22:04 ` [Buildroot] [PATCH 00/16] Bump ejabberd version to 17.04 Thomas Petazzoni
2017-05-31  8:49   ` Johan Oudinet

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=20170531111936.79596357@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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