From: Tomas Volf <~@wolfsden.cz>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: #:modules and #:imported-modules, and more
Date: Wed, 10 Jan 2024 17:43:08 +0100 [thread overview]
Message-ID: <ZZ7JHEKde2Ecy7JP@ws> (raw)
In-Reply-To: <87wmshv65h.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 941 bytes --]
On 2024-01-10 11:23:22 +0100, Ludovic Courtès wrote:
> Hi!
>
> Tomas Volf <~@wolfsden.cz> skribis:
>
> > However even in that light, I still consider the 3 and 4 to be worth
> > considering. Aaand even without 3, at least doing 4 in some shape or form would
> > be in my opinion useful. Current situation is bit... copy&pasty.
>
> In ‘core-updates’, commit 9e4ce281dbd92e3c52b831824ebb1f77023c960c by
> Maxim should address these concerns (IIUC) by distinguishing and
> renaming the variables for the default set of imported and in-scope
> modules for ‘gnu-build-system’.
>
> Is that one of the things you had in mind?
Ah, yes, thank you for pointing that commit out, pretty much that, just for all
the build systems (it seems only gnu-build-system was modified on core-updates).
Tomas
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-01-10 16:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-30 12:54 #:modules and #:imported-modules, and more Tomas Volf
2024-01-09 22:49 ` Ludovic Courtès
2024-01-09 23:09 ` Tomas Volf
2024-01-10 10:23 ` Ludovic Courtès
2024-01-10 16:43 ` Tomas Volf [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
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=ZZ7JHEKde2Ecy7JP@ws \
--to=~@wolfsden.cz \
--cc=guix-devel@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 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).