From: sbromberger <sbromberger@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New packages: ipsvd, socklog-ucspi
Date: Thu, 29 Dec 2022 17:58:17 +0100 [thread overview]
Message-ID: <20221229165817.oVkrztDYRItbm4jBNnxvAcTPDJ9Q6nW4LTjXXVaw3xQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41321@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 569 bytes --]
New comment by sbromberger on void-packages repository
https://github.com/void-linux/void-packages/pull/41321#issuecomment-1367463354
Comment:
> Void depends are only for essential dependencies, if you configure socklog to use tcpsvd, it's your problem to have the appropriate tools installed.
Interesting. I hadn't thought of it this way before. In this case perhaps it's better to not create a runfile that is broken by default? If the user has to go through the steps of installing tcpsvd, then s/he is probably adept enough to create an appropriate service.
next prev parent reply other threads:[~2022-12-29 16:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 0:13 [PR PATCH] socklog: depend on ipsvd for ucspi-tcp service kruceter
2022-12-28 0:25 ` [PR PATCH] [Updated] " kruceter
2022-12-28 0:27 ` kruceter
2022-12-28 19:47 ` leahneukirchen
2022-12-28 19:48 ` leahneukirchen
2022-12-28 20:58 ` [PR PATCH] [Updated] " kruceter
2022-12-29 3:00 ` New packages: ipsvd, socklog-ucspi sbromberger
2022-12-29 5:44 ` sbromberger
2022-12-29 5:45 ` sbromberger
2022-12-29 5:45 ` sbromberger
2022-12-29 8:00 ` kruceter
2022-12-29 16:32 ` leahneukirchen
2022-12-29 16:58 ` sbromberger [this message]
2022-12-29 22:32 ` kruceter
2022-12-29 22:33 ` [PR PATCH] [Updated] " kruceter
2023-01-02 15:19 ` [PR PATCH] [Merged]: " leahneukirchen
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=20221229165817.oVkrztDYRItbm4jBNnxvAcTPDJ9Q6nW4LTjXXVaw3xQ@z \
--to=sbromberger@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).