From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: "Steve Litt" <slitt@troubleshooters.com>, supervision@list.skarnet.org
Subject: Re: Can s6 be enough?: was s6-ps
Date: Tue, 08 Jan 2019 09:19:36 +0000 [thread overview]
Message-ID: <em120c1764-bd34-4e5b-816f-e7f138d2a446@elzian> (raw)
In-Reply-To: <20190107164506.0d925cd9@mydesk.domain.cxm>
>When Debian acquires a properly working s6-rc package, the answer to my
>question degenerates to "why not?" But for now, for the Debian person
>who only installs via package, s6-rc is out of the question, so my
>question was, isn't s6 itself good enough?
Then maybe you should ask Debian instead, "why aren't you packaging
s6-rc?"
It's literally a distribution's *job* to package software that may
be useful to users. And instead, you are bending your mind to try
and find justifications for users not to use some software, for the
simple reason that it's not packaged by a distribution. That logic
is 100% backwards.
You want to help users? Package s6-rc for Debian. Also, call out
Debian on their prejudice and disingenuous use of policies that
prevent people from making correct execline and s6 packages.
--
Laurent
next prev parent reply other threads:[~2019-01-08 9:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9f647c4c-2dc3-b977-928c-ee164ba88afe@ntlworld.com>
2019-01-05 0:20 ` s6-ps Laurent Bercot
2019-01-05 4:04 ` s6-ps Jonathan de Boyne Pollard
2019-01-05 10:46 ` s6-ps Jonathan de Boyne Pollard
2019-01-05 14:41 ` s6-ps Jonathan de Boyne Pollard
2019-01-05 15:29 ` s6-ps multiplexd
2019-01-05 20:30 ` Can s6 be enough?: was s6-ps Steve Litt
2019-01-05 21:22 ` Laurent Bercot
[not found] ` <20190106053901.GA16647@latitude.localdomain>
2019-01-06 7:40 ` Laurent Bercot
2019-01-06 15:03 ` Brett Neumeier
2019-01-07 21:45 ` Steve Litt
2019-01-08 9:19 ` Laurent Bercot [this message]
2019-01-05 21:00 ` s6-ps Guillermo
2019-01-06 1:15 ` s6-ps Steve Litt
2019-01-06 7:06 ` s6-ps Colin Booth
2019-01-06 7:30 ` s6-ps Laurent Bercot
2019-01-06 18:07 ` s6-ps Colin Booth
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=em120c1764-bd34-4e5b-816f-e7f138d2a446@elzian \
--to=ska-supervision@skarnet.org \
--cc=slitt@troubleshooters.com \
--cc=supervision@list.skarnet.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).