From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] shadowsocks-libev: new package
Date: Mon, 4 Jun 2018 18:00:30 +0200 [thread overview]
Message-ID: <20180604160030.GC3700@scaer> (raw)
In-Reply-To: <20180604120908.0f340f5e@windsurf>
Min, Thomas, All,
On 2018-06-04 12:09 +0200, Thomas Petazzoni spake thusly:
> On Mon, 4 Jun 2018 00:16:26 -0700, Min Xu wrote:
[--SNIP--]
> > diff --git a/package/shadowsocks-libev/0001-docs-add-BSD-3-Clause-licence.patch b/package/shadowsocks-libev/0001-docs-add-BSD-3-Clause-licence.patch
> > new file mode 100644
> > index 0000000..64dda02
> > --- /dev/null
> > +++ b/package/shadowsocks-libev/0001-docs-add-BSD-3-Clause-licence.patch
> > @@ -0,0 +1,52 @@
> > +From 0047295445c499e010706598c50f1bff8b0d632c Mon Sep 17 00:00:00 2001
> > +From: Min Xu <xuminready@gmail.com>
> > +Date: Wed, 30 May 2018 13:16:12 -0700
> > +Subject: [PATCH] docs: add BSD-3-Clause licence
> > +
> > +add missing licence for shadowsocks-libev/libipset
> > +
> > +Signed-off-by: Min Xu <xuminready@gmail.com>
>
> I'm still not entirely convinced by a patch adding a license file. It
> would definitely be useful to convince upstream to add this license
> file, but I'm not sure we want to carry patches in Buildroot adding
> license files.
>
> Peter, Arnout, Yann, any comment on this ?
I agree with Thomas here: do not add a license file ourselves (unless we
backport an upstream commit, in which case the patch should say so).
If the package does not have a license file, then just include a source
file, preferrably a prominent one like main.c or whatever.
And above all, better no information that bad information. So, don;t add
the license file.
Regards,
Yann E. MORIN.
> > +SHADOWSOCKS_LIBEV_VERSION = 3.2.0
> > +SHADOWSOCKS_LIBEV_SITE = https://github.com/shadowsocks/shadowsocks-libev/releases/download/v$(SHADOWSOCKS_LIBEV_VERSION)
> > +SHADOWSOCKS_LIBEV_LICENSE = GPL-3.0+, BSD-2-Clause(libbloom), BSD-3-Clause(libcork, libipset)
> > +SHADOWSOCKS_LIBEV_LICENSE_FILES = COPYING libbloom/LICENSE libcork/COPYING libipset/LICENSE.txt
> > +SHADOWSOCKS_LIBEV_DEPENDENCIES = host-pkgconf c-ares libev libsodium mbedtls pcre
> > +SHADOWSOCKS_LIBEV_INSTALL_STAGING = YES
> > +SHADOWSOCKS_LIBEV_CONF_OPTS = --disable-documentation --with-pcre=$(STAGING_DIR)/usr
>
> --disable-documentation is already passed by the autotools-package
> infrastructure, so it isn't needed.
>
> Besides those minor issues, the rest looks good to me. Thanks!
>
> Thomas
> --
> Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
> Embedded Linux and Kernel engineering
> https://bootlin.com
--
.-----------------.--------------------.------------------.--------------------.
| 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-04 16:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 7:16 [Buildroot] [PATCH] shadowsocks-libev: new package Min Xu
2018-06-04 10:09 ` Thomas Petazzoni
2018-06-04 16:00 ` Yann E. MORIN [this message]
2018-06-04 22:07 ` Arnout Vandecappelle
2018-06-05 6:50 ` xu min
2018-06-04 20:34 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2018-05-29 6:55 Min Xu
2018-05-30 20:52 ` 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=20180604160030.GC3700@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.