From: Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM>
To: Supervision <supervision@list.skarnet.org>
Cc: Charlie Brady <charlieb-supervision@budge.apana.org.au>
Subject: Re: Compatibilities between runit and s6 (re: Incompatibilities between runit and s6?)
Date: Tue, 16 Jan 2018 21:51:51 +0000 [thread overview]
Message-ID: <3c9e4d86-5f14-2110-e99f-95afa2a87ba1@NTLWorld.COM> (raw)
In-Reply-To: <Pine.LNX.4.64.1801161056250.25033@e-smith.charliebrady.org>
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
Charlie Brady:
> OK, so this statement is incomplete:
>
It also does not tell you that you need other POSIX-standard commands
such as |mv| and |ln|. But you need them, too. I draw the line at
listing every command, that POSIX-conformant systems have had to have
for two decades and that are also listed in the Linux Standard Base
<https://refspecs.linuxfoundation.org/LSB_5.0.0/LSB-Common/LSB-Common/rcommands.html>,
that is required. That would be ridiculous. I also don't mention
things that /operating system doco/ says are fundamental for building
packages, like build-essential
<https://www.debian.org/doc/manuals/maint-guide/start.en.html#needprogs>
and base-devel
<https://wiki.archlinux.org/index.php/Creating_Packages#Prerequisite_software>.
Pointing out that you need |redo|, on the other hand, is pointing out
something that is not POSIX, not in the LSB, and not in the operating
system doco. On those grounds, I should add that you need |xmlto|.
next prev parent reply other threads:[~2018-01-16 21:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 23:23 Incompatibilities between runit and s6? Avery Payne
2018-01-11 14:14 ` Charlie Brady
2018-01-13 18:03 ` Compatibilities between runit and s6 (re: Incompatibilities between runit and s6?) Charlie Brady
2018-01-13 18:55 ` Laurent Bercot
2018-01-14 11:36 ` Jonathan de Boyne Pollard
2018-01-14 21:08 ` Charlie Brady
2018-01-14 21:54 ` Jonathan de Boyne Pollard
2018-01-15 12:53 ` Thomas Caravia
2018-01-15 13:33 ` Laurent Bercot
2018-01-16 0:33 ` Charlie Brady
2018-01-16 0:44 ` nosh build problems (Re: Compatibilities between runit and s6 (re: ) Charlie Brady
2018-01-16 16:09 ` Charlie Brady
2018-01-16 20:51 ` Jonathan de Boyne Pollard
2018-01-17 1:26 ` Guillermo
2018-01-17 7:35 ` Jonathan de Boyne Pollard
2018-01-17 15:25 ` Charlie Brady
2018-01-18 11:58 ` Guillermo
2018-01-18 14:25 ` nosh build problems (Re: Compatibilities between runit and s6 Charlie Brady
2018-02-18 21:16 ` nosh build problems (Re: Compatibilities between runit and s6 (re: ) Guillermo
2018-01-16 8:10 ` Compatibilities between runit and s6 (re: Incompatibilities between runit and s6?) Jonathan de Boyne Pollard
2018-01-16 15:59 ` Charlie Brady
2018-01-16 21:51 ` Jonathan de Boyne Pollard [this message]
2018-01-16 8:06 ` Jonathan de Boyne Pollard
2018-01-16 14:52 ` multiplexd
[not found] ` <89cffa18-a72a-ed98-031c-c72fc00ad5aa@ntlworld.com>
2018-01-16 15:44 ` Laurent Bercot
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=3c9e4d86-5f14-2110-e99f-95afa2a87ba1@NTLWorld.COM \
--to=j.deboynepollard-newsgroups@ntlworld.com \
--cc=charlieb-supervision@budge.apana.org.au \
--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).