From: "Ludovic Courtès" <ludo@gnu.org>
To: guix-devel <guix-devel@gnu.org>
Subject: The GNU Shepherd 0.9.0rc1 available for testing!
Date: Wed, 30 Mar 2022 18:59:33 +0200 [thread overview]
Message-ID: <87r16jtlze.fsf@gnu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1554 bytes --]
Hello Guix!
A release candidate of the Shepherd 0.9.0 is available for testing!
https://alpha.gnu.org/gnu/shepherd/shepherd-0.9.0rc1.tar.gz
https://alpha.gnu.org/gnu/shepherd/shepherd-0.9.0rc1.tar.gz.sig
SHA256: 6b7cdbb8d2509fca0c4d08b855031ea72c887a65828ae6493c2e5a25130c3c37
You can test it on Guix System with:
guix time-machine --branch=wip-shepherd-upgrade -- \
system reconfigure …
and on Guix Home:
guix time-machine --branch=wip-shepherd-upgrade -- \
home reconfigure …
Bug reports are most welcome.
The branch changes the ‘ssh-daemon’ service to an inetd-style service:
https://git.savannah.gnu.org/cgit/guix.git/log?h=wip-shepherd-upgrade
You’re welcome to propose patches to change other services to systemd or
inetd style.
The ‘make-forkexec-constructor/container’ procedure that we have doesn’t
compose well (we’d have to make
‘make-inetd-forkexec-constructor/container’, etc.). But I think we
could achieve the same thing differently, with wrappers, so that we can
have inetd and systemd services running in containers too. Future work…
There’s also more work we can do in future Shepherd versions, such as
adding ‘herd journal SERVICE’, moving state out of <service>, adding a
REPL :-), etc., but what we have today is a reasonable milestone IMO.
Besides, a new POT file should be available soon if you’d like to help
translate the new release in your language:
https://translationproject.org/domain/shepherd.html
Ludo’.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 853 bytes --]
next reply other threads:[~2022-03-30 16:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 16:59 Ludovic Courtès [this message]
2022-04-04 2:33 ` The GNU Shepherd 0.9.0rc1 available for testing! Maxim Cournoyer
2022-04-05 12:41 ` Ludovic Courtès
2022-04-06 16:25 ` Maxim Cournoyer
2022-04-04 8:40 ` pelzflorian (Florian Pelz)
2022-04-05 12:39 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r16jtlze.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).