all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Tue, 31 Oct 2023 17:03:57 +0000	[thread overview]
Message-ID: <1Lbh6LTUAZI1rid93lHYEmdZBeToprn9DZBarBpj5-WQnOYRdJ7oaUAoAumjFsr8cOmX8XOTci4g_jcbTGEtYKe6qTf-Nk8lFK7D-0NYpzs=@lendvai.name> (raw)
In-Reply-To: <7d9c1d64af2c747e68a9d78b955e1411bee99f90.1690641116.git.attila@lendvai.name>

Ludo, any hope that this gets merged?

i'm trying to debug something in shepherd (the SYSTEM call in shepherd misbehaves, but only when pulled on my server, not in a `guix system vm`). it will once again require me to use a custom shepherd, and pull/rebuild/reconfigure a gazillion times.

as for this patch: the only issue i know is that it cannot be cross compiled because of the help2man call. if you ask me, i would just get rid of that altogether. it's just added complexity for little gain.

--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“He who flatters a man is his enemy. He who tells him of his faults is his maker.”
	— Confucius (551–479 BC)





  reply	other threads:[~2023-10-31 17:04 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 [this message]
2023-11-05 14:47     ` Ludovic Courtès
2023-11-13  9:38       ` Attila Lendvai
2023-11-17 15:26         ` 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='1Lbh6LTUAZI1rid93lHYEmdZBeToprn9DZBarBpj5-WQnOYRdJ7oaUAoAumjFsr8cOmX8XOTci4g_jcbTGEtYKe6qTf-Nk8lFK7D-0NYpzs=@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.