Github messages for voidlinux
 help / color / mirror / Atom feed
From: CameronNemo <CameronNemo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] Update FRRouting
Date: Sat, 12 Sep 2020 19:39:30 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24850@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 391 bytes --]

There is a new pull request by CameronNemo against master on the void-packages repository

https://github.com/CameronNemo/void-packages libyang-1.0.184
https://github.com/void-linux/void-packages/pull/24850

Update FRRouting
Updates frr and its dependency libyang.

Cross builds are enabled for frr.

A patch file from https://github.com/void-linux/void-packages/pull/24850.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-libyang-1.0.184-24850.patch --]
[-- Type: text/x-diff, Size: 4086 bytes --]

From 56e020f15c34ba7ecb470de83af0051f8e318210 Mon Sep 17 00:00:00 2001
From: Cameron Nemo <cnemo@tutanota.com>
Date: Sat, 12 Sep 2020 09:58:48 -0700
Subject: [PATCH 1/2] libyang: update to 1.0.184.

---
 srcpkgs/libyang/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/libyang/template b/srcpkgs/libyang/template
index 7d25508cfb6..ddcc3a84e5b 100644
--- a/srcpkgs/libyang/template
+++ b/srcpkgs/libyang/template
@@ -1,6 +1,6 @@
 # Template file for 'libyang'
 pkgname=libyang
-version=1.0.167
+version=1.0.184
 revision=1
 build_style=cmake
 configure_args="-DENABLE_LYD_PRIV=ON"
@@ -11,7 +11,7 @@ maintainer="Cameron Nemo <cnemo@tutanota.com>"
 license="BSD-3-Clause"
 homepage="https://github.com/CESNET/libyang"
 distfiles="https://github.com/CESNET/libyang/archive/v${version}.tar.gz"
-checksum=2431fa5c7cfbe6a6f2c0873547b976f018438967adfe268726911dd3d95eaa31
+checksum=1a5637451b73c4c5683837eb4c51371bb084795f653bc1a5fc20fed5541b58bc
 
 post_install() {
 	vlicense LICENSE

From 067bdce58b35061838b99456e0d9c422fb485d2a Mon Sep 17 00:00:00 2001
From: Cameron Nemo <cnemo@tutanota.com>
Date: Sat, 12 Sep 2020 10:38:17 -0700
Subject: [PATCH 2/2] frr: update to 7.4.

Also enable cross builds using the new --with-clippy option.
---
 srcpkgs/frr-devel    |  1 +
 srcpkgs/frr/template | 30 ++++++++++++++++++++++++------
 2 files changed, 25 insertions(+), 6 deletions(-)
 create mode 120000 srcpkgs/frr-devel

diff --git a/srcpkgs/frr-devel b/srcpkgs/frr-devel
new file mode 120000
index 00000000000..6060b277e4e
--- /dev/null
+++ b/srcpkgs/frr-devel
@@ -0,0 +1 @@
+frr
\ No newline at end of file
diff --git a/srcpkgs/frr/template b/srcpkgs/frr/template
index 019022d486b..2989adf98b2 100644
--- a/srcpkgs/frr/template
+++ b/srcpkgs/frr/template
@@ -1,7 +1,7 @@
 # Template file for 'frr'
 pkgname=frr
-version=7.3.1
-revision=2
+version=7.4
+revision=1
 wrksrc="${pkgname}-${pkgname}-${version}"
 build_style=gnu-configure
 # chroot-texinfo is not able to build frr's docs
@@ -13,17 +13,16 @@ make_build_args="SPHINXBUILD=sphinx-build3"
 conf_files="/etc/frr/*.conf"
 make_dirs="/var/log/frr 0700 _frr _frr"
 hostmakedepends="pkg-config flex bison autoconf automake libtool
- python python3 python3-Sphinx python-devel python3-devel libyang-tools"
+ python3 python3-Sphinx python3-devel libyang-tools"
 makedepends="pcre-devel libcap-devel json-c-devel pam-devel c-ares-devel
- readline-devel python-devel python3-devel libyang-devel"
+ readline-devel python3-devel libyang-devel"
 short_desc="IP routing protocol suite"
 maintainer="Cameron Nemo <cnemo@tutanota.com>"
 license="GPL-2.0-or-later, LGPL-2.1-or-later"
 homepage="https://frrouting.org"
 distfiles="https://github.com/FRRouting/frr/archive/${pkgname}-${version}.tar.gz"
-checksum=81129f83ce9ae31c983bb02b3d8e3e457604bab46f01411c945d9c2cfef1f5c8
+checksum=3c8204fda1c9b178d8446562579bbbc49d134b98f3ad02aa56f68724a2f9e40a
 python_version=3
-nocross="http://ix.io/1rQ6"
 system_groups="_frrvty"
 system_accounts="_frr"
 _frr_groups="_frrvty"
@@ -34,11 +33,23 @@ if [ "$XBPS_TARGET_LIBC" = "musl" ]; then
 	makedepends+=" musl-legacy-compat"
 fi
 
+subpackages="libfrrospfapiclient libfrrospfapiclient-devel libfrr libfrr-devel frr-flush frr-reload"
+if [ "$CROSS_BUILD" ]; then
+	hostmakedepends+=" frr-devel"
+	configure_args+=" --with-clippy=/usr/libexec/frr-devel/clippy"
+else
+	subpackages+=" frr-devel"
+fi
+
 pre_configure() {
 	autoreconf -fi
 }
 
 post_install() {
+	if [ -z "$CROSS_BUILD" ]; then
+		# install build tool to be used by cross builds
+		vinstall lib/clippy 0755 usr/libexec/frr-devel
+	fi
 	# LSB init script and friends are not needed
 	for cmd in frr watchfrr watchfrr.sh frrcommon.sh frrinit.sh generate_support_bundle.py; do
 		rm -f -- "${DESTDIR}/usr/bin/${cmd}"
@@ -58,6 +69,13 @@ post_install() {
 	done
 }
 
+frr-devel_package() {
+	short_desc+=" (development binaries)"
+	pkg_install() {
+		vmove usr/libexec/frr-devel
+	}
+}
+
 frr-flush_package() {
 	short_desc+=" - route flushing tool"
 	depends="iproute2 ${sourcepkg}-${version}_${revision}"

             reply	other threads:[~2020-09-12 17:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-12 17:39 CameronNemo [this message]
2020-09-15 18:36 ` [PR PATCH] [Merged]: " ahesford

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24850@inbox.vuxu.org \
    --to=cameronnemo@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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;
as well as URLs for NNTP newsgroup(s).