From: Bruno Victal <mirai@makinata.eu>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>, guix-devel@gnu.org
Subject: Re: Divvying up service definitions
Date: Tue, 28 Nov 2023 20:29:43 +0000 [thread overview]
Message-ID: <fbaa4873-2a6b-4fc3-bd9c-ba0961ed0bb8@makinata.eu> (raw)
In-Reply-To: <ZUyHEZq_AU-0HFj7@3900XT>
[-- Attachment #1.1: Type: text/plain, Size: 759 bytes --]
Hi Efraim,
On 2023-11-09 07:15, Efraim Flashner wrote:
> I assume the define-maybe's aren't public, so I'd guess that shouldn't
> cause a problem as long as they aren't exported.
They're not public but they override definitions within the same file
if more than one (define-maybe foo) is present (e.g. when (prefix bar-)
is used)
> Or moving the define-maybes to the top of the file and reusing them
> between services. Is that a possibility?
Due to their non-hygienic nature and the (prefix foo-) argument this
can't work. IMO we should look into replacing this define-maybe business
with something like SRFI-189 (by integrating it into Guile).
--
Furthermore, I consider that nonfree software must be eradicated.
Cheers,
Bruno.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-11-28 20:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 14:41 Divvying up service definitions Bruno Victal
2023-10-24 17:54 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-10-26 15:09 ` Bruno Victal
2023-10-28 9:11 ` Attila Lendvai
2023-11-09 14:55 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-11-07 15:56 ` Maxim Cournoyer
2023-11-09 7:15 ` Efraim Flashner
2023-11-28 20:29 ` Bruno Victal [this message]
2023-12-05 1:23 ` Maxim Cournoyer
2023-11-16 14:49 ` 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
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=fbaa4873-2a6b-4fc3-bd9c-ba0961ed0bb8@makinata.eu \
--to=mirai@makinata.eu \
--cc=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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).