[bug#61750] [PATCH] gnu: shepherd: Build Shepherd from git.

[Attila Lendvai]

> but after having read the README once again, i'm still not sure how this 
> would work. please confirm my assumption:
> 
> if i add shepherd as a channel, then i unavoidably need to issue a `guix 
> pull` (slow!) before i can test any shepherd changes, even if the channel 
> points to a local checkout. also, i need to record any pending changes that i 
> want to test into a git commit.


FTR, i've made progress, and i think i'm back to my original routine.

what i was missing is adding this to my guix .envrc:

export GUILE_LOAD_PATH=~/workspace/guix/shepherd/.guix/modules:$GUILE_LOAD_PATH

this then enables the following:

(define *parent-shepherd-package* (@ (shepherd-package) shepherd))

with this shepherd package i can once again start a `guix system vm` with all 
the changes in my shepherd checkout compiled in, and with a bearable turnaround 
time.

note that this was not suggested in the README. i'll keep an eye on updating 
the docs to help others getting into shepherd hacking.

thanks for your patience and help Ludo!

-- 
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“When a wise man points at the moon the imbecile examines the finger.”
        — Confucius (551–479 BC)