From: CameronNemo <CameronNemo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] network-ups-tools: do not ship binaries in /var
Date: Fri, 14 Aug 2020 04:38:43 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24265@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 468 bytes --]
There is a new pull request by CameronNemo against master on the void-packages repository
https://github.com/CameronNemo/void-packages NUT
https://github.com/void-linux/void-packages/pull/24265
network-ups-tools: do not ship binaries in /var
In Debian these are shipped in /lib/nut,
which is equivalent to /usr/libexec/nut on Void.
Binaries certainly do not belong in /var.
A patch file from https://github.com/void-linux/void-packages/pull/24265.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-NUT-24265.patch --]
[-- Type: text/x-diff, Size: 1451 bytes --]
From e3763ceff377b16cf337528d782ee2652d8bdd92 Mon Sep 17 00:00:00 2001
From: Cameron Nemo <cnemo@tutanota.com>
Date: Thu, 13 Aug 2020 19:36:13 -0700
Subject: [PATCH] network-ups-tools: do not ship binaries in /var
In Debian these are shipped in /lib/nut,
which is equivalent to /usr/libexec/nut on Void.
Binaries certainly do not belong in /var.
---
srcpkgs/network-ups-tools/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/network-ups-tools/template b/srcpkgs/network-ups-tools/template
index 6582e8d3f9b..cc100bbde6e 100644
--- a/srcpkgs/network-ups-tools/template
+++ b/srcpkgs/network-ups-tools/template
@@ -1,7 +1,7 @@
# Template file for 'network-ups-tools'
pkgname=network-ups-tools
version=2.7.4
-revision=9
+revision=10
wrksrc="nut-${version}"
build_style=gnu-configure
configure_args="
@@ -9,7 +9,7 @@ configure_args="
--datadir=/usr/share/ups --with-user=nut --with-group=nut --with-ssl
--with-usb --with-dev --with-serial -with-avahi --with-udev-dir=/usr/lib/udev
--with-libltdl --without-ipmi --without-freeipmi --without-systemdsystemunitdir
- --with-snmp --with-drvpath=/var/lib/nut $(vopt_with cgi) --with-statepath=/run/ups"
+ --with-snmp --with-drvpath=/usr/libexec/nut $(vopt_with cgi) --with-statepath=/run/ups"
hostmakedepends="pkg-config"
makedepends="avahi-libs-devel libressl-devel libusb-compat-devel neon-devel
net-snmp-devel $(vopt_if cgi gd-devel) libltdl-devel"
next reply other threads:[~2020-08-14 2:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 2:38 CameronNemo [this message]
2020-08-14 2:50 ` ahesford
2020-09-07 23:20 ` network-ups-tools: add warning about FHS violation ahesford
2020-09-07 23:34 ` CameronNemo
2020-09-07 23:44 ` ahesford
2020-09-07 23:44 ` [PR PATCH] [Closed]: " 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-24265@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).