From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: Bruno Victal <mirai@makinata.eu>, 66426@debbugs.gnu.org
Subject: [bug#66426] [PATCH 00/65] Export %default-gnu-imported-modules and %default-gnu-modules.
Date: Tue, 10 Oct 2023 06:14:36 +0200 [thread overview]
Message-ID: <833f6e7be42b6fd505d2cdd401e93f0d9b64bab7.camel@gmail.com> (raw)
In-Reply-To: <87fs2j8dqa.fsf@gmail.com>
Am Montag, dem 09.10.2023 um 21:31 -0400 schrieb Maxim Cournoyer:
> Hi Liliana,
>
> Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
> > Hmm, at the very least I'd like to bikeshed the variable names,
> > hence my suggestion to encode it into the build system itself,
> > which would allow any name locally. %default-anything reads weird
> > to me, plus it's a mouthful for imported modules.
>
> It seems conventional to me: we have %default-subtitute-urls,
> %default-channels, %default-include (thousands of matches for
> '%default-' upon grepping).
Fair enough, but in the cases you've named it's still %default for more
than one build system. Or do you by extension want %default-glib-or-
gtk-imported-modules? That's quite a mouthful imho without any
additional semantics.
> > WDYT about %gnu-build-modules and %gnu-build-system-modules, where
> > %gnu-build-system-modules keeps its current intent for being
> > imported?
> > Alternatively we could also rename it to %gnu-build-imported-
> > modules
> > with a deprecated alias.
>
> People have been adding %gnu-build-system-modules to #:modules
> erroneously. Not renaming that would ensure this keeps happening.
> Having 'imported-modules' in the name seems like it'd make things a
> bit easier to remember; thus, I think the proposed naming is
> adequate?
Perhaps, but I think %gnu-build-modules and %gnu-build-imported-modules
is better even with that reasoning.
Cheers
next prev parent reply other threads:[~2023-10-10 4:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1696868939.git.maxim.cournoyer@gmail.com>
2023-10-09 18:18 ` [bug#66426] [PATCH 00/65] Export %default-gnu-imported-modules and %default-gnu-modules Liliana Marie Prikler
2023-10-09 19:36 ` Maxim Cournoyer
2023-10-09 19:45 ` Liliana Marie Prikler
2023-10-10 1:31 ` Maxim Cournoyer
2023-10-10 4:14 ` Liliana Marie Prikler [this message]
2023-10-10 14:36 ` Maxim Cournoyer
2023-10-16 15:28 ` Maxim Cournoyer
2023-10-19 4:04 ` bug#66426: " Maxim Cournoyer
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=833f6e7be42b6fd505d2cdd401e93f0d9b64bab7.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=66426@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=mirai@makinata.eu \
/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).