From: zmudc <zmudc@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: tigervnc: a working runit service for the tigervnc vncserver cannot be written
Date: Thu, 17 Aug 2023 23:51:49 +0200 [thread overview]
Message-ID: <20230817215149.4p5OT8twsgI305aPz8QSlJwWEy4VqRYWx006SPXgzpU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45522@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 778 bytes --]
New comment by zmudc on void-packages repository
https://github.com/void-linux/void-packages/issues/45522#issuecomment-1683026736
Comment:
> I don't see why upstream wouldn't accept a simple "don't daemonize" flag, which carries essentially no maintenance burden on them, doesn't involve ensuring that it works with any supervisor, and would generally be useful for debugging anyway.
Well, I guess we can wait and see if they review the PR I submitted upstream in which I point out there is not much much cost to adding the flag. So far, they have ignored the PR, and their comments about supporting non-systemd systems are not encouraging. Essentially, upstream is saying, "it's not our bug, it is downstream's bug if downstream can't use a systemd Type=forking service."
next prev parent reply other threads:[~2023-08-17 21:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 15:44 [ISSUE] tigervnc: multiple patches needed to create a working runit service for the tigervnc vncserver zmudc
2023-08-17 21:32 ` tigervnc: a working runit service for the tigervnc vncserver cannot be written zmudc
2023-08-17 21:44 ` ahesford
2023-08-17 21:51 ` zmudc [this message]
2023-10-03 22:57 ` ahesford
2023-10-03 22:57 ` [ISSUE] [CLOSED] " ahesford
2023-10-04 0:08 ` ahesford
2023-10-04 13:36 ` zmudc
2023-10-04 13:55 ` 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=20230817215149.4p5OT8twsgI305aPz8QSlJwWEy4VqRYWx006SPXgzpU@z \
--to=zmudc@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).