From: Attila Lendvai <attila@lendvai.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 61750@debbugs.gnu.org
Subject: [bug#61750] [PATCH] gnu: shepherd: Build Shepherd from git.
Date: Fri, 17 Nov 2023 15:26:32 +0000 [thread overview]
Message-ID: <nKmvUPGtAXw7pf7PbIS2dHs6sNwdo_RbWsKz0IRXVD76RaEjBh5XfejHvvq0HBevpAIc3i8LamFPPERe0dFtFhXmASBPRecp0PnvRA018cA=@lendvai.name> (raw)
In-Reply-To: <jcQ2CBnKpBoKokQQqZOszB_UzKoGrbUmAEDHXmDYr5xKuV7AqYJZE_0ALVNK78unZkbIJTFyQlWkcNsgL7MvxYebxnnhg_rzXDF9nXxapiQ=@lendvai.name>
> 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)
prev parent reply other threads:[~2023-11-17 15:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 14:02 [bug#61750] [PATCH 1/2] gnu: shepherd: Build Shepherd from git Attila Lendvai
2023-02-24 14:07 ` [bug#61750] [PATCH 2/2] WIP failing attempt to get the man page while cross-compiling Attila Lendvai
2023-07-29 14:31 ` [bug#61750] [PATCH] gnu: shepherd: Build Shepherd from git Attila Lendvai
2023-10-31 17:03 ` Attila Lendvai
2023-11-05 14:47 ` Ludovic Courtès
2023-11-13 9:38 ` Attila Lendvai
2023-11-17 15:26 ` Attila Lendvai [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='nKmvUPGtAXw7pf7PbIS2dHs6sNwdo_RbWsKz0IRXVD76RaEjBh5XfejHvvq0HBevpAIc3i8LamFPPERe0dFtFhXmASBPRecp0PnvRA018cA=@lendvai.name' \
--to=attila@lendvai.name \
--cc=61750@debbugs.gnu.org \
--cc=ludo@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.