From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: network-ups-tools: add warning about FHS violation
Date: Tue, 08 Sep 2020 01:20:42 +0200 [thread overview]
Message-ID: <20200907232042.Kif-RaXY7OsU3a2thydudthFMhQRkVYMPh9dnm1dJbg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24265@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 693 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/24265#issuecomment-688538017
Comment:
I've looked at the source code and see no reason why `/usr/libexec/nut` would behave any differently than `/var/lib/nut`. Furthremore, this uses a flag provided directly by the configure script, so we can probably have faith that upstream has tested the path specification mechanism. I'm content to merge your original patch at e3763ce if you don't object, knowing we can always revert the change if somebody reports an issue.
If you don't want the blame for this change, I'll merge an equivalent change in my own name. Let me know what you prefer.
next prev parent reply other threads:[~2020-09-07 23:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 2:38 [PR PATCH] network-ups-tools: do not ship binaries in /var CameronNemo
2020-08-14 2:50 ` ahesford
2020-09-07 23:20 ` ahesford [this message]
2020-09-07 23:34 ` network-ups-tools: add warning about FHS violation 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=20200907232042.Kif-RaXY7OsU3a2thydudthFMhQRkVYMPh9dnm1dJbg@z \
--to=ahesford@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).