supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM>
Cc: Supervision <supervision@list.skarnet.org>
Subject: The shape of things to come
Date: Sun, 4 Feb 2018 06:16:56 +0000	[thread overview]
Message-ID: <77024052-fe28-0dd8-47f0-6c2ff5fcdbc4@NTLWorld.COM> (raw)

To let you know in advance, Thomas:

In 1.37, a pre-relase source archive for which will be available for you 
later today in the usual place, I am making several changes.

Several of your patches are going to be shorter or even entirely moot.  
The build system will try to explicitly pick some .service.arch-linux 
files when it detects Arch Linux.  Please check that I have got these right.

I finally need to have pre-install and post-remove maintenance actions, 
because of D-Bus in Debian 9.  So I have re-vamped the maintenance 
script generation.  You should find it easier to map the new system onto 
Arch Linux, as the Debian file naming system is now closer to the BSD 
one.  Please adjust as required.  Have a look at the new 
package/debian/gencontrol for pointers to adjustments for your 
scriptletbuilder.  Notice that there's now no occasion where there is a 
wholesale override script, nor is there any occasion where there is no 
.funcs file.  Also beware that you'll need to patch out dpkg-divert in 
nosh-service-management.*.extra and the dbusprefix in package/stage.



                 reply	other threads:[~2018-02-04  6:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=77024052-fe28-0dd8-47f0-6c2ff5fcdbc4@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).