From: Maxime Devos <maximedevos@telenet.be>
To: Attila Lendvai <attila@lendvai.name>, 54199@debbugs.gnu.org
Subject: [bug#54199] [PATCH] doc: Add 'Working on Shepherd' section.
Date: Mon, 28 Feb 2022 20:38:36 +0100 [thread overview]
Message-ID: <cfb14eda0845cab93da71a68172eda67be1a36e7.camel@telenet.be> (raw)
In-Reply-To: <20220228185115.28042-1-attila@lendvai.name>
[-- Attachment #1: Type: text/plain, Size: 1370 bytes --]
Attila Lendvai schreef op ma 28-02-2022 om 19:51 [+0100]:
> +custom Shepherd package for an @code{operating-system} object. To get a
> +customized Shepherd package, you can simply make a copy of it in
> +@file{gnu/packages/admin.scm}, and change the @code{source} and
> +@code{version} field along these lines:
> +
> +@lisp
> +(define-public shepherd-dev-pid-1
> + (package
> + (name "shepherd")
> + (version "dev-pid-1")
> + (source (git-checkout
> + (url "file:///my/path/shepherd/")))
> + ...
> + ))
There's no need to make a copy, we can use inheritance here
to reduce duplication:
(define my-shepherd
(package
(inherit shepherd)
(source (git-checkout
(url "file:///my/path/shepherd/"))))
Also, we're missing autoconf & friends here?
To help with shepherd hacking, I think it would be ok to add them to
the standard 'shepherd' package with a nice comment. If not, a
'shepherd-next' package or the like could be defined, a variant
of 'shepherd' for building from git?
Also, the documentation is being inconsistent with versions here.
In one place, you're using "dev-pid-1", and in another, "dev".
These versions also seem a bit odd for not being version _numbers_,
which doesn't mesh well with '17.4.3 Version Numbers'.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-02-28 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 18:51 [bug#54199] [PATCH] doc: Add 'Working on Shepherd' section Attila Lendvai
2022-02-28 19:31 ` Maxime Devos
2022-02-28 19:38 ` Maxime Devos [this message]
2022-03-01 10:14 ` pelzflorian (Florian Pelz)
2022-05-02 11:11 ` Attila Lendvai
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=cfb14eda0845cab93da71a68172eda67be1a36e7.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=54199@debbugs.gnu.org \
--cc=attila@lendvai.name \
/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.