> Relatedly, does anyone have a nicer workflow they use to define and
> test shepherd services?
i'm not sure it's a nicer workflow, but i'm mimicing the Guix tests:
https://github.com/attila-lendvai/guix-crypto/blob/main/tests/swarm-tests.scm#L19
it is based on `guix system vm` and the testing i
> (shepherd-service
> (start
> #~(make-forkexec-constructor
> some-command
> #:directory (pk #$twgter-directory)
> #:log-file (pk #$twgter-log-file))
> ))
>
> If we instantiate this process in our OS declaration under services
> and then run that OS inside a container and `herd start
> this-servic
Hello. Is it possible to get better error reporting in the following
example?
$ sudo guix system -K -L /home/vlad/Code/fullmeta-guix/channel container
os.scm
And our os.scm imports some services defined in our channel above. Should
there be an error in one of them, however, the stack trace only t
> Hello. Is it possible to get better error reporting in the following
> example?
>
> $ sudo guix system -K -L /home/vlad/Code/fullmeta-guix/channel container
> os.scm
>
> [...]
I also face this very problem when using the "-L" switch with other
commands, e.g. `guix shell`. Is there some missed-
