From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: shepherd -> guile 2.2?
Date: Wed, 17 May 2017 15:02:28 +0200 [thread overview]
Message-ID: <87fug3y6u3.fsf@gnu.org> (raw)
In-Reply-To: <878tlx5h10.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 16 May 2017 10:42:51 +0200")
Hi Ricardo,
Ricardo Wurmus <rekado@elephly.net> skribis:
> I have built shepherd with guile-2.2, but I noticed a couple of
> warnings/errors during the build:
I’m pretty sure those warnings are due to IOFBF and friends. They’ll
haunt us for years to come. :-)
(But you can happily ignore them.)
> And lastly: should we keep a guile-2.0 variant of the shepherd, or is it
> fine to push this tiny change?
No, we can do that in ‘core-updates’ only.
The reason is that we import code in the Shepherd, via the gexps in the
‘start’ and ‘stop’ fields of <shepherd-service>, and those modules are
currently built with ‘default-guile’, which is 2.0 in master and 2.2 in
‘core-updates’.
So yeah, in ‘core-updates’, we can happily move the Shepherd and mcron
to 2.2, but not in ‘master’.
Ludo’.
prev parent reply other threads:[~2017-05-17 13:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 8:42 shepherd -> guile 2.2? Ricardo Wurmus
2017-05-16 10:45 ` Andy Wingo
2017-05-16 13:47 ` Fox
2017-05-17 13:02 ` Ludovic Courtès [this message]
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=87fug3y6u3.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).