all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Thu, 21 Nov 2024 16:21:55 +0000	[thread overview]
Message-ID: <f344c832-f1e9-48af-b6b6-05ec074be630@posteo.net> (raw)
In-Reply-To: <87jzcyyygp.fsf@gnu.org>

Hi,

On 20.11.24 11:46, Ludovic Courtès wrote:

> 
>> Another (simpler solution) would be to just solve the problem in guix
>> by using a shepherd variant that deletes sbin and share/man/man8.
> 
> Yes, this sounds like a reasonable solution to me.
> 
> Ludo’.

How should this work? should this be a (public?) procedure? Should it 
rebuild shepherd or just copy the output with trivial-build-system?


I just thought of a more elegant solution, but this would be a lot 
harder to implement properly:

- Move the sbin stuff into a seperate output
- Home shepherd service only adds the main output to the profile and 
shepherd-root-service both
- Will need adjustments some packages that currently reference 
shutdown/reboot ( -> lots of rebuilds because logind) and the same 
change for the shepherd packages in the shepherd module.




      reply	other threads:[~2024-11-21 16:23 UTC|newest]

Thread overview: 6+ 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
2024-11-20 10:46     ` Ludovic Courtès
2024-11-21 16:21       ` Dariqq [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=f344c832-f1e9-48af-b6b6-05ec074be630@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.