All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joachim Wiberg <troglobit@gmail.com>
To: buildroot@buildroot.org
Cc: Joachim Wiberg <troglobit@gmail.com>,
	Matt Weber <matthew.weber@collins.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: [Buildroot] [PATCH v2 0/3] bump smcroute and add start script
Date: Mon, 30 Aug 2021 17:30:53 +0200	[thread overview]
Message-ID: <20210830153056.3176678-1-troglobit@gmail.com> (raw)

Hi everyone!

This is the third version of the patch to update SMCRoute to the latest
version.  Previous versions were audited by Yegor and Thomas, thank you
for that!  There is a fresh bug fix release upstream and this patch set
has been updated to reflect that.

Also, there is now a SysV start script included, installed when a SysV
init is used.  The upstream systemd unit file was already instaled when
systemd is used.  Both of them support an optional /etc/default/smcroute
environment file that is sourced before starting smcrouted, for site
local cmdline options.

Basic tests pass:

    $ ./utils/check-package package/smcroute/*
    56 lines processed
    0 warnings generated
    $ ./utils/test-pkg -c smcroute.config -p smcroute
                        bootlin-armv5-uclibc [1/6]: OK
                         bootlin-armv7-glibc [2/6]: OK
                       bootlin-armv7m-uclibc [3/6]: SKIPPED
                         bootlin-x86-64-musl [4/6]: OK
                          br-arm-full-static [5/6]: OK
                                sourcery-arm [6/6]: OK
    6 builds, 1 skipped, 0 build failed, 0 legal-info failed

To verify the integration, manual testing from a clean master branch,
has been performed in Qemu (Aarch64) using with both BusyBox init and
systemd.

Best regards
 /Joachim

Reviewed-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Signed-off-by: Joachim Wiberg <troglobit@gmail.com>

---
v2:
 - fixed incorrect use of global CFLAGS in .mk (Thomas)
 - bump to latest upstream, v2.5.2
 - add sysv init script with optional /etc/default/smcroute
 - clean up compat script wrapper post-install

Joachim Wiberg (3):
  package/smcroute: bump version to v2.5.2
  package/smcroute: add sysv init script
  package/smcroute: prune old smcroute compat script

 package/smcroute/S41smcroute   | 48 ++++++++++++++++++++++++++++++++++
 package/smcroute/smcroute.hash |  7 ++---
 package/smcroute/smcroute.mk   | 18 +++++++++----
 3 files changed, 65 insertions(+), 8 deletions(-)
 create mode 100755 package/smcroute/S41smcroute

-- 
2.25.1

_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

             reply	other threads:[~2021-08-30 15:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-30 15:30 Joachim Wiberg [this message]
2021-08-30 15:30 ` [Buildroot] [PATCH v2 1/3] package/smcroute: bump version to v2.5.2 Joachim Wiberg
2021-09-11 14:31   ` Arnout Vandecappelle
2021-08-30 15:30 ` [Buildroot] [PATCH v2 2/3] package/smcroute: add sysv init script Joachim Wiberg
2021-09-11 14:33   ` Arnout Vandecappelle
2021-09-28  7:43     ` Joachim Wiberg
2021-08-30 15:30 ` [Buildroot] [PATCH v2 3/3] package/smcroute: prune old smcroute compat script Joachim Wiberg

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=20210830153056.3176678-1-troglobit@gmail.com \
    --to=troglobit@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=matthew.weber@collins.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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.