From: ScrelliCopter <ScrelliCopter@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] net-tools: update to 2.10
Date: Fri, 08 Jan 2021 05:27:35 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27755@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 723 bytes --]
There is a new pull request by ScrelliCopter against master on the void-packages repository
https://github.com/ScrelliCopter/void-packages net-tools
https://github.com/void-linux/void-packages/pull/27755
net-tools: update to 2.10
Upstream has [tagged a new release](https://github.com/ecki/net-tools/releases/tag/v2.10) which removes the need for for using a Git revision and allows the template to be simplified. I've also made other changes that are required for the new version to build.
However this release is only a day old at the time of writing so I'm marking this as a draft until there's enough confidence to switch.
A patch file from https://github.com/void-linux/void-packages/pull/27755.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-net-tools-27755.patch --]
[-- Type: text/x-diff, Size: 1456 bytes --]
From f397404e7e9c36df5244ad958c8226e1dbd038b3 Mon Sep 17 00:00:00 2001
From: a dinosaur <nick@a-dinosaur.com>
Date: Fri, 8 Jan 2021 15:16:30 +1100
Subject: [PATCH] net-tools: update to 2.10
---
srcpkgs/net-tools/template | 10 ++++------
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/srcpkgs/net-tools/template b/srcpkgs/net-tools/template
index 384feba77fb..f93d123f8ce 100644
--- a/srcpkgs/net-tools/template
+++ b/srcpkgs/net-tools/template
@@ -1,15 +1,13 @@
# Template file for 'net-tools'
pkgname=net-tools
-version=1.60.20181103git
+version=2.10
revision=1
-_githash=0eebece8c964e3cfa8a018f42b2e7e751a7009a0
-wrksrc="${pkgname}-${_githash}"
short_desc="Basic networking tools"
maintainer="Orphaned <orphan@voidlinux.org>"
license="GPL-2.0-or-later"
homepage="https://github.com/ecki/net-tools"
-distfiles="https://github.com/ecki/net-tools/archive/${_githash}.tar.gz"
-checksum=795cb4dd2618ed7ff9a48b9cb63b33780b47dfd7464c8e52ba734e6796cbab17
+distfiles="${homepage}/archive/v${version}.tar.gz"
+checksum=8e186f65f0ff304989b3dc8b0067c3a07d36ae777da60667bdd6ccb2730908d2
alternatives="
ifconfig:ifconfig:/usr/bin/${pkgname}-ifconfig
@@ -40,7 +38,7 @@ do_build() {
}
do_install() {
- make DESTDIR=${DESTDIR}/usr update
+ make DESTDIR=${DESTDIR}/usr install
# Rename ifconfig for alternatives.
mv ${DESTDIR}/usr/bin/{ifconfig,${pkgname}-ifconfig}
mv ${DESTDIR}/usr/share/man/man8/{ifconfig,${pkgname}-ifconfig}.8
next reply other threads:[~2021-01-08 4:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 4:27 ScrelliCopter [this message]
2021-02-15 4:04 ` ericonr
2021-02-15 19:46 ` ScrelliCopter
2021-02-15 19:46 ` ScrelliCopter
2021-02-15 19:48 ` [PR PATCH] [Updated] " ScrelliCopter
2021-10-12 5:59 ` ScrelliCopter
2021-10-12 5:59 ` [PR PATCH] [Closed]: " ScrelliCopter
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-27755@inbox.vuxu.org \
--to=screllicopter@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).