From: Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM>
To: Supervision <supervision@list.skarnet.org>
Subject: Re: Compatibilities between runit and s6 (re: Incompatibilities between runit and s6?)
Date: Sun, 14 Jan 2018 21:54:42 +0000 [thread overview]
Message-ID: <d5e13aae-b461-16ac-33da-139c2ed4a240@NTLWorld.COM> (raw)
In-Reply-To: <Pine.LNX.4.64.1801141607370.14234@e-smith.charliebrady.org>
[-- Attachment #1: Type: text/plain, Size: 2080 bytes --]
Jonathan de Boyne Pollard:
> The |service-manager| manual page from version 1.37 or later of the
> nosh toolset contains a full breakdown of the control/status API in a
> |supervise/| directory, including the daemontools-encore extensions
> and the nosh service-manager's own extensions. I am hoping to get
> version 1.37 released within the next week. In the meantime, I have
> pushed the new manual page to the on-line copy of the /nosh Guide/
> <http://jdebp.info./Softwares/nosh/>. You can find the HTML-form
> manual page for |service-manager| hyperlinked from several pages in
> the /Guide/, including the _new Interfaces_ page.
>
Charlie Brady:
> Do you know whether anyone has documented how to build on a non-Debian
> linux? An rpm spec file would be ideal, but just simple non-Debian
> centric build instructions would be better than nothing.
>
Yes. I have. The slashpackage-style build instructions, which are of
course /not/ Debian-specific nor even /Linux-/specific, are actually
right there on the source package WWW page.
The only thing that is Debian-specific is the step that gets one from a
/built/ slashpackage-style package to Debian binary packages. This is
in the supplied |package/debian/rules| command. But even that is not
actually Debian-specific, as there is a similar |package/bsd/rules|
command that does the same thing on the BSDs.
Thomas Caravia constructed the Archnosh PKGBUILD the same way. It does
the slashpackage-style build, then takes the built slashpackage-style
package and parcels it out into a set of Arch binary packages, with a
light dusting of patches to a handful of service bundles. It even
mostly re-uses the Debian maintenance scripts.
(On that note, Thomas: You may enjoy the start that I have made in 1.37
to a _Packages and Ports_ chapter in the /nosh Guide/. Yes, I currenly
plan for the |.p|/|.func| system to get at least a short mention.)
I was only expecting you to read the manual for doco on the common
control/status API that you were interested in, not build the software. (-:
next prev parent reply other threads:[~2018-01-14 21:54 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 [this message]
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
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=d5e13aae-b461-16ac-33da-139c2ed4a240@NTLWorld.COM \
--to=j.deboynepollard-newsgroups@ntlworld.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).