Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] shadowsocks-libev: new package
Date: Mon, 4 Jun 2018 22:34:43 +0200	[thread overview]
Message-ID: <20180604223443.3b130018@windsurf> (raw)
In-Reply-To: <20180604071626.17528-1-xuminready@gmail.com>

Hello,

On Mon,  4 Jun 2018 00:16:26 -0700, Min Xu wrote:
> Shadowsocks-libev is a lightweight secured SOCKS5 proxy for
> embedded devices and low-end boxes.
> 
> https://github.com/shadowsocks/shadowsocks-libev
> 
> A patch for BSD-3-Clause licence for libipset is added. It's from libipset's git repo.
> 
> Signed-off-by: Min Xu <xuminready@gmail.com>
> ---
>  package/Config.in                                  |  1 +
>  .../0001-docs-add-BSD-3-Clause-licence.patch       | 52 ++++++++++++++++++++++
>  package/shadowsocks-libev/Config.in                | 12 +++++
>  package/shadowsocks-libev/shadowsocks-libev.hash   |  8 ++++
>  package/shadowsocks-libev/shadowsocks-libev.mk     | 15 +++++++
>  5 files changed, 88 insertions(+)
>  create mode 100644 package/shadowsocks-libev/0001-docs-add-BSD-3-Clause-licence.patch
>  create mode 100644 package/shadowsocks-libev/Config.in
>  create mode 100644 package/shadowsocks-libev/shadowsocks-libev.hash
>  create mode 100644 package/shadowsocks-libev/shadowsocks-libev.mk

I've applied to master, after doing the following changes:

    [Thomas:
     - drop patch adding license file for libipset
     - drop --disable-documentation, it's passed by autotools-package
     - add entry in DEVELOPERS file
     - pass --disable-ssp because the SSP check uses AC_COMPILE_IFELSE()
       so with some toolchains, it think SSP support is available, while
       it's not. And anyway we want SSP to be controlled by Buildroot
       global options, not on a per-package basis.
     - add depends on BR2_USE_MMU, because the code uses fork().]

Thanks for this contribution!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2018-06-04 20:34 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
2018-06-04 22:07     ` Arnout Vandecappelle
2018-06-05  6:50       ` xu min
2018-06-04 20:34 ` Thomas Petazzoni [this message]
  -- 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=20180604223443.3b130018@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