From: abenson <abenson@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] chrony: allow specifying additional options
Date: Tue, 14 Mar 2023 18:54:47 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42768@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 502 bytes --]
There is a new pull request by abenson against master on the void-packages repository
https://github.com/abenson/void-packages chronyd_options
https://github.com/void-linux/void-packages/pull/42768
chrony: allow specifying additional options
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, x86_64
A patch file from https://github.com/void-linux/void-packages/pull/42768.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-chronyd_options-42768.patch --]
[-- Type: text/x-diff, Size: 1156 bytes --]
From 0d2d66c2582b74ed6696af7443cbc1060938f62b Mon Sep 17 00:00:00 2001
From: Andrew Benson <abenson+void@gmail.com>
Date: Tue, 14 Mar 2023 12:53:19 -0500
Subject: [PATCH] chrony: allow specifying additional options
---
srcpkgs/chrony/files/chronyd/run | 3 ++-
srcpkgs/chrony/template | 2 +-
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/chrony/files/chronyd/run b/srcpkgs/chrony/files/chronyd/run
index a6aeb85624ce..c26b42a1fec0 100644
--- a/srcpkgs/chrony/files/chronyd/run
+++ b/srcpkgs/chrony/files/chronyd/run
@@ -1,4 +1,5 @@
#!/bin/sh
exec 2>&1
+[ -r conf ] && . ./conf
install -d -m750 -o chrony -g chrony /var/run/chrony
-exec chronyd -n -u chrony
+exec chronyd -n -u chrony ${OPTS}
diff --git a/srcpkgs/chrony/template b/srcpkgs/chrony/template
index b0c51cc263fa..758965f7bce2 100644
--- a/srcpkgs/chrony/template
+++ b/srcpkgs/chrony/template
@@ -2,7 +2,7 @@
# When Updating: Please confirm the upstream config still refers to make_dirs
pkgname=chrony
version=4.3
-revision=1
+revision=2
build_style=gnu-configure
configure_args="--without-nss --enable-scfilter
--with-sendmail=/usr/bin/sendmail"
next reply other threads:[~2023-03-14 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 17:54 abenson [this message]
2023-03-14 18:09 ` [PR PATCH] [Merged]: " abenson
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-42768@inbox.vuxu.org \
--to=abenson@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).