From: slymattz <slymattz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: openvpn: update to 2.6.9.
Date: Thu, 22 Feb 2024 16:12:13 +0100 [thread overview]
Message-ID: <20240222151213.E227123E24@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48693@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]
New comment by slymattz on void-packages repository
https://github.com/void-linux/void-packages/pull/48693#issuecomment-1959656887
Comment:
> (...) I think we should better do this in a other PR to allow further discussions about it there, so that it won't block this update. Feel free to create one 👍
Whoever reviews this PR, please bear in mind that I had no intention of hindering this OpenVPN update by opening up a discussion here - https://github.com/void-linux/void-packages/issues/48834
I believe keeping OpenVPN up-to-date is important regardless of the conclusions drawn in the aforementioned discussion. That being said, it would be nice to have a runit service installed in /usr/share/examples/sv/openvpn in one of the future updates (see https://github.com/void-linux/void-packages/issues/48834#issuecomment-1953063448). One argument for doing so is that the service would be easily accessible to users who want to have it enabled on boot. And on top of that the proposed solution would be safe for those who run OpenVPN manually or use NetworkManager etc.
next prev parent reply other threads:[~2024-02-22 15:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 11:33 [PR PATCH] " Bnyro
2024-02-18 19:47 ` slymattz
2024-02-18 21:33 ` Bnyro
2024-02-18 21:56 ` slymattz
2024-02-18 21:56 ` slymattz
2024-02-18 22:36 ` Bnyro
2024-02-19 17:44 ` slymattz
2024-02-22 15:12 ` slymattz [this message]
2024-03-04 19:27 ` slymattz
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=20240222151213.E227123E24@inbox.vuxu.org \
--to=slymattz@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).