Re: shepherd -> guile 2.2?

[Andy Wingo <wingo@igalia.com>]

On Tue 16 May 2017 10:42, Ricardo Wurmus <rekado@elephly.net> writes:

> ;;; WARNING: compilation of /gnu/store/5zx29y44nrqj0s8h3jlvlj82k8hj4dxs-guile-2.2.2/bin/guild failed:
> ;;; ERROR: failed to create path for auto-compiled file "/gnu/store/5zx29y44nrqj0s8h3jlvlj82k8hj4dxs-guile-2.2.2/bin/guild"

This is because the build does not set XDG_CACHE_HOME.  See:

  https://lists.gnu.org/archive/html/guix-devel/2017-02/msg00939.html

> Some deprecated features have been used.  Set the environment
> variable GUILE_WARN_DEPRECATED to "detailed" and rerun the
> program to get more information.  Set it to "no" to suppress
> this message.

Here you will get more info if you set the
GUILE_WARN_DEPRECATED=detailed variable.

> shepherd/support.scm:209:2: warning: non-literal format string

Not a deal-breaker; worth having a look at though.

> shepherd/runlevel.scm:106:6: warning: possibly unbound variable `next-services'

Something to look into.

> shepherd/service.scm:606:8: warning: possibly unbound variable `apply-to-args'

Replace with "apply".

> And lastly: should we keep a guile-2.0 variant of the shepherd, or is it
> fine to push this tiny change?

I would say don't bother keeping it.

Andy