From: ludo@gnu.org (Ludovic Courtès)
To: "Stefan Reichör" <stefan@xsteve.at>
Cc: 28531@debbugs.gnu.org
Subject: [bug#28531] [PATCH] gnu: Add vcsh.
Date: Sat, 23 Sep 2017 14:52:14 +0200 [thread overview]
Message-ID: <87vak9a875.fsf@gnu.org> (raw)
In-Reply-To: <87o9q2o1bw.fsf@xsteve.at> ("Stefan \=\?utf-8\?Q\?Reich\=C3\=B6r\=22\?\= \=\?utf-8\?Q\?'s\?\= message of "Fri, 22 Sep 2017 23:44:35 +0200")
Hello,
Stefan Reichör <stefan@xsteve.at> skribis:
>> Hi Stefan,
>>
>> Stefan Reichör <stefan@xsteve.at> skribis:
>>
>>> * gnu/packages/version-control.scm (vcsh): New variable.
>>
>> Pushed with the minor changes below (the first sentence of the
>> description looked awkward to me).
>>
>> Note that vcsh takes ‘git’ from $PATH. I wonder if we should keep it
>> this way, or if we should hard-code the absolute file name to ‘git’ so
>> that it always works.
>>
>> Thoughts?
>
> I don't think that it is desirable to change all external tool
> invocations for programs in Guix. I am currently preparing the tool
> atool that has to invoke a lot of archivers.
We always have a choice between “static binding” (where we hard-wire a
tool and its dependencies) and “late binding” (where the dependencies
are searched for at run time.)
Most of the time in Guix we favor static binding: it makes sure that (1)
programs work out of the box, regardless of what happens to be already
installed on your system, and (2) that the program will behave the same
on all systems since its behavior does not depend on external state.
There are exceptions where we want dynamic binding, for instance for
plugins or optional/soft dependencies.
The case of ‘vcsh’ is borderline. I have a slight preference to
hardwire the dependency on Git (after all, someone might want to use
vcsh without having installed Git before), but I’m open to other
arguments.
Thoughts?
Thanks,
Ludo’.
PS: Please preserve Cc:.
next prev parent reply other threads:[~2017-09-23 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 19:37 [bug#28531] [PATCH] gnu: Add vcsh Stefan Reichör
2017-09-20 20:32 ` bug#28531: " Ludovic Courtès
[not found] ` <87o9q2o1bw.fsf@xsteve.at>
2017-09-23 12:52 ` Ludovic Courtès [this message]
2017-09-23 18:10 ` [bug#28531] " Stefan Reichör
2017-09-25 9:50 ` 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=87vak9a875.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=28531@debbugs.gnu.org \
--cc=stefan@xsteve.at \
/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).