From: "Ludovic Courtès" <ludo@gnu.org>
To: <guix-devel@gnu.org>
Subject: Shepherd 1.0.0rc1 available for testing!
Date: Sun, 10 Nov 2024 00:23:19 +0100 [thread overview]
Message-ID: <87jzdcxa8o.fsf@gnu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 4225 bytes --]
Hello Guix!
I finally tagged 1.0.0rc1! (I was planning to have Fibers bug fixes
checked in and published first, but after much effort, I chose to invert
priorities.)
Looks like we might have one or two bugs already from Felix, we’ll see.
The tarball and signature are available at:
https://alpha.gnu.org/gnu/shepherd/shepherd-1.0.0rc1.tar.gz
SHA256: 3ce5d60e528d4cfb282b1f271a601256395b28f16e41be6052cf5945f687b004
https://alpha.gnu.org/gnu/shepherd/shepherd-1.0.0rc1.tar.gz.sig
The tarball was meant from v1.0.0rc1
(aka. 49f5330077393715ff7e1625be039f64724825d2) and should be
bit-for-bit reproducible (run “make dist” from ‘guix shell -CP’).
What’s new
==========
Check out the ‘NEWS’ file to see what you might enjoy:
https://git.savannah.gnu.org/cgit/shepherd.git/tree/NEWS
How to test
===========
You could still a reference to the tarball above in your Guix checkout,
but the preferred way is probably to use Shepherd as a channel, as noted
in ‘README’:
The Shepherd repository can be used as a Guix “channel”. To do that, change
~/.config/guix/channels.scm along these lines:
(append (list (channel
(name 'shepherd)
(url "https://git.savannah.gnu.org/git/shepherd.git")
(branch "main")
(introduction
(make-channel-introduction
"788a6d6f1d5c170db68aa4bbfb77024fdc468ed3"
(openpgp-fingerprint
"3CE464558A84FDC69DB40CFB090B11993D9AEBB5")))))
%default-channels)
Once that is done, run ‘guix pull’. This will give you additional ‘shepherd’
packages with higher version numbers:
guix package -A shepherd
You can then install it with ‘guix install shepherd’, or e.g. use it in an
operating-system configuration:
(operating-system
...
(essential-services
(modify-services (operating-system-default-essential-services
this-operating-system)
(shepherd-root-service-type
config =>
(shepherd-configuration
(inherit config)
(shepherd (@ (shepherd-package) shepherd)))))))
To test with Guix Home:
(home-environment
(services
(list (service home-shepherd-service-type
(home-shepherd-configuration
(shepherd (@ (shepherd-package) shepherd))))
…)))
Testing the new services
========================
Among the highlights of 1.0.0 are the new ‘system-log’ and
‘log-rotation’ services. Testing them requires more changes to your
config but feedback would be welcome!
First, you can define these two services in your Guix System config:
(define system-log-service-type
(shepherd-service-type
'shepherd-system-log
(const (shepherd-service
(documentation "Shepherd's built-in system log (syslogd).")
(provision '(system-log syslogd))
(modules '((shepherd service system-log)))
(free-form #~(system-log-service))))
#t
(description
"Shepherd's built-in system log (syslogd).")))
(define log-rotation-service
(simple-service 'shepherd-log-rotation
shepherd-root-service-type
(list (shepherd-service
(provision '(log-rotation))
(modules '((shepherd service log-rotation)))
(free-form #~(log-rotation-service))))))
Then you can actually use one or both:
(operating-system
;; …
(services (cons* log-rotation-service
(service system-log-service-type)
;; …
;; Remove the currently-used syslogd service,
;; now redundant.
(modify-services %desktop-services
(delete syslog-service-type)))))
Reporting bugs
==============
Please email bug-guix@gnu.org with “[Shepherd]” in the subject to report
bugs.
Translation
===========
Consider helping with translation of messages at
<https://translationproject.org/domain/shepherd.html>.
Thanks in advance. :-)
Ludo’.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 853 bytes --]
next reply other threads:[~2024-11-09 23:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-09 23:23 Ludovic Courtès [this message]
2024-11-11 11:15 ` Shepherd 1.0.0rc1 available for testing! pelzflorian (Florian Pelz)
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=87jzdcxa8o.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).