From: Attila Lendvai <attila@lendvai.name>
To: Attila Lendvai <attila@lendvai.name>
Cc: 54216@debbugs.gnu.org
Subject: [bug#54216] [PATCH staging v3] gnu: shepherd: Build it from git, and clean up shepherd-for-guix.
Date: Tue, 22 Mar 2022 09:27:42 +0000 [thread overview]
Message-ID: <SokeY0oKL5bbY9xBcY1RGeaM8zb5XHt97Rjy8SUPmm3UGJY_XmeT56stjEJ9BQ0yP9caHnv9EeuYiDtBMBoSieizmGpietfLiGbq6eEHXaI=@lendvai.name> (raw)
In-Reply-To: <20220321170716.20140-1-attila@lendvai.name>
just a quick idea:
another solution could be to introduce a shepherd-tools package that only contains the command line tools, and packages would depend on this one, not shepherd itself.
that way shepherd could be updated cheaply, and as long as the socket interface remains compatible, the shepherd-tools package doesn't need to be updated (which is expensive in the current dependency graph).
--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“I cannot imagine a torture more vicious and terrifying than to realize in the face of one’s final days that one wasted his entire life trying to please the plethora of idiots around him, instead of educating them and himself and molding tomorrow for the better.”
— Brandon Smith, 'Alt-Market blog'
next prev parent reply other threads:[~2022-03-22 9:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 18:28 [bug#54216] [PATCH] gnu: shepherd-for-guix: New package for use in Guix Attila Lendvai
2022-03-01 18:36 ` Maxime Devos
2022-03-01 18:45 ` [bug#54216] [PATCH v2] " Attila Lendvai
2022-03-01 19:01 ` Maxime Devos
2022-03-01 19:27 ` Attila Lendvai
2022-03-02 9:14 ` zimoun
2022-03-02 23:50 ` Leo Famulari
2022-03-03 6:25 ` Maxime Devos
2022-03-03 8:48 ` zimoun
2022-03-05 21:13 ` Leo Famulari
2022-03-05 21:50 ` Maxime Devos
2022-03-03 14:36 ` [bug#54216] [PATCH staging] gnu: shepherd: Build it from git, and clean up shepherd-for-guix Maxime Devos
2022-03-03 14:51 ` zimoun
2022-03-03 9:43 ` [bug#54216] [PATCH v3] gnu: shepherd-for-guix: New package for use in Guix Attila Lendvai
2022-03-03 14:28 ` [bug#54216] [PATCH staging] gnu: shepherd: Build it from git, and clean up shepherd-for-guix Attila Lendvai
2022-03-04 10:30 ` [bug#54216] [PATCH shepherd staging v2] " Attila Lendvai
2022-03-21 15:14 ` [bug#54216] [PATCH v4] gnu: shepherd-for-guix: New package for use in Guix Attila Lendvai
2022-03-21 15:41 ` [bug#54216] [PATCH] " Ludovic Courtès
2022-03-21 16:12 ` zimoun
2022-03-21 17:07 ` [bug#54216] [PATCH staging v3] gnu: shepherd: Build it from git, and clean up shepherd-for-guix Attila Lendvai
2022-03-22 9:27 ` Attila Lendvai [this message]
2022-03-22 13:48 ` Attila Lendvai
2022-03-22 14:42 ` pelzflorian (Florian Pelz)
2022-03-28 9:07 ` Attila Lendvai
2022-05-01 14:31 ` [bug#54216] [PATCH v4] gnu: shepherd: Build Shepherd 0.9.0 from git Attila Lendvai
2022-09-26 19:11 ` [bug#54216] [PATCH v5] gnu: shepherd: Build Shepherd 0.9.2 " Attila Lendvai
2022-09-26 21:44 ` [bug#54216] [PATCH v6] " 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='SokeY0oKL5bbY9xBcY1RGeaM8zb5XHt97Rjy8SUPmm3UGJY_XmeT56stjEJ9BQ0yP9caHnv9EeuYiDtBMBoSieizmGpietfLiGbq6eEHXaI=@lendvai.name' \
--to=attila@lendvai.name \
--cc=54216@debbugs.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).