From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: 'package-name-version' and 'strip-store-file-name' does the same thing with different ways
Date: Sat, 20 Oct 2018 15:57:34 +0200 [thread overview]
Message-ID: <87woqc90vl.fsf@gnu.org> (raw)
In-Reply-To: <871s8l2evi.fsf@elephly.net> (Ricardo Wurmus's message of "Sat, 20 Oct 2018 10:37:05 +0200")
Ricardo Wurmus <rekado@elephly.net> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>>> Similarly, 'file-sans-extension' are defined in both (guix utils) and
>>> (guix build guile-build-system). They are both the same. Should we move
>>> them to (guix build utils) as well?
>>
>> Yes, sounds like a good idea!
>
> ‘file-sans-extension’ is used on the host-side, e.g. in scripts/build.scm.
> Is it still fine to move it to a build-side module only?
I think so because in practice we already use (guix build utils) quite a
lot on the “host side”.
More generally, while I think it’s important to arrange things so that
we don’t end up importing all of Guix on the build side, the advantage
of using the same language on both sides is that we can share code. I
think we should take advantage of it when there are no downsides.
Ludo’.
prev parent reply other threads:[~2018-10-20 13:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 19:26 'package-name-version' and 'strip-store-file-name' does the same thing with different ways Alex Vong
2018-10-16 11:54 ` Ludovic Courtès
2018-10-16 22:04 ` Alex Vong
2018-10-19 13:52 ` Ludovic Courtès
2018-10-19 18:28 ` Alex Vong
2018-10-20 13:24 ` Ludovic Courtès
2018-10-20 8:37 ` Ricardo Wurmus
2018-10-20 13:57 ` Ludovic Courtès [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=87woqc90vl.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).