From: Dariqq <dariqq@posteo.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 73903@debbugs.gnu.org
Subject: bug#73903: [shepherd]: Guix Home's shepherd masks shutdown/reboot on foreign distribution
Date: Sun, 10 Nov 2024 15:57:54 +0000 [thread overview]
Message-ID: <e1746555-6ef6-4a7c-970e-007bdd5c91ab@posteo.net> (raw)
In-Reply-To: <87a5e7wbmf.fsf@gnu.org>
Hi Ludo,
On 10.11.24 12:51, Ludovic Courtès wrote:
> Hi,
>
> Dariqq <dariqq@posteo.net> skribis:
>
>> When using guix home to manage shepherd services on a foreign
>> distribution the shepherd package is also added to the home-profile.
>>
>> This then makes the home profile provide 'halt', 'shutdown' and
>> 'reboot' (and their manpages) masking the system ones.
>
> Oh, indeed. I’m not sure how to address that though. Ideas?
>
Not sure if this is something that should be addressed by shepherd or
the default shepherd package used for guix home.
Initially I had the idea to add a configure flag to shepherd to disable
"building" and installing these 5 files (which is why I reported against
shepherd). I threw something together that works but I am not really
happy with it because imo such an option should disable *all*
things that are not required when only using it for user level
services and not just the entrypoints. That would be a lot more work though.
Another (simpler solution) would be to just solve the problem in guix by
using a shepherd variant that deletes sbin and share/man/man8.
Wdyt?
> Ludo’.
next prev parent reply other threads:[~2024-11-10 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-20 10:12 bug#73903: [shepherd]: Guix Home's shepherd masks shutdown/reboot on foreign distribution Dariqq
2024-11-06 13:52 ` bug#73903: (no subject) Jakob Honal via Bug reports for GNU Guix
2024-11-10 11:51 ` bug#73903: [shepherd]: Guix Home's shepherd masks shutdown/reboot on foreign distribution Ludovic Courtès
2024-11-10 15:57 ` Dariqq [this message]
2024-11-20 10:46 ` Ludovic Courtès
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=e1746555-6ef6-4a7c-970e-007bdd5c91ab@posteo.net \
--to=dariqq@posteo.net \
--cc=73903@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.