supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Laurent Bercot <ska-skaware-csDn2i8iPApAfugRpC6u6w@public.gmane.org>
To: skaware-cfaJnhaL+FNC7f45DRzWBg@public.gmane.org,
	supervision-cfaJnhaL+FNC7f45DRzWBg@public.gmane.org
Subject: announce: skalibs-1.2.8, execline-1.1.5, s6-0.17
Date: Tue, 12 Jun 2012 15:52:38 +0200	[thread overview]
Message-ID: <20120612135238.GA31022@skarnet.org> (raw)

(batch announcement, also sent to the supervision mailing-list because
s6-0.17 depends on the other two.)

 Hello,

 skalibs-1.2.8 is out.
 It fixes a few portability bugs - most importantly, a clock accuracy
bug appearing on some libcs. Also, nonblocking zero-copy data transfer
now works on Linux no matter the libc.

 http://www.skarnet.org/software/skalibs/


 execline-1.1.5 is out.
 It adds functionality to backtick, forx and forbacktickx: you now have
the option to make the variable an environment variable instead of a
substitution macro. This behaviour will become the default at some point
in the future, so you are advised to upgrade and update your scripts
with explicit options !
 Note for repackagers: the binaries now include compile-time-coded
paths to other execline binaries, so be careful and patch appropriately
if you are moving the binaries outside of the installation convention.

 http://www.skarnet.org/software/execline/


 s6-0.17 is out.
 It fixes a stupid bug in s6-svstat, and cleans up a bit of code.
With the new skalibs, "echo | s6-tai64n | s6-tai64nlocal" should now
give the same time as "date" on every correctly configured system.

 http://www.skarnet.org/software/s6/

 Enjoy,
 Bug-reports welcome.

-- 
 Laurent


                 reply	other threads:[~2012-06-12 13:52 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=20120612135238.GA31022@skarnet.org \
    --to=ska-skaware-csdn2i8ipapafugrpc6u6w@public.gmane.org \
    --cc=skaware-cfaJnhaL+FNC7f45DRzWBg@public.gmane.org \
    --cc=supervision-cfaJnhaL+FNC7f45DRzWBg@public.gmane.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).