From: Ricardo Wurmus <rekado@elephly.net>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel@gnu.org
Subject: Re: How to reference external program used in shell-scripts?
Date: Sun, 08 Sep 2019 21:08:00 +0200 [thread overview]
Message-ID: <87lfuy4ne7.fsf@elephly.net> (raw)
In-Reply-To: <d40b7d9b-8938-c541-006e-6eef3f773f6d@crazy-compilers.com>
Hartmut Goebel <h.goebel@crazy-compilers.com> writes:
> Am 03.09.19 um 15:01 schrieb Ludovic Courtès:
>> The whole idea of functional software deployment is that it’s stateless:
>> you can tell that /gnu/store/…-ansible-1.2.3 will always behave the
>> same, no matter what other programs are available on your machine.
>>
>> Introducing “dynamic binding” (e.g., looking up programs in $PATH) would
>> allow for faster security updates in the example you gave, but that
>> would be at the expense of that core property I described above. It
>> would be a regression.
>>
>> I think what we need in this case is (1) fast security updates, which is
>> what grafts help us achieve, and (2) documentation that clarifies what
>> the deployment model is, such that Mary would know that ‘ansible’ also
>> needs to be upgraded in the example above.
>
> I understand this.
>
> Anyway: IMHO missing "dynamic binding" is one of the major drawbacks of
> functional deployment, as it requires updating (and esp. downloading)
> much more packages compared to a rpm/deb based system.
At the same time static binding is also one of the major advantages as
deployments are stateless and thus much more predictable, reliable, and
inspectable.
--
Ricardo
next prev parent reply other threads:[~2019-09-08 19:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 13:14 How to reference external program used in shell-scripts? Hartmut Goebel
2019-08-08 14:50 ` Ricardo Wurmus
2019-08-09 8:03 ` Hartmut Goebel
2019-08-09 8:54 ` Ricardo Wurmus
2019-09-03 9:08 ` Hartmut Goebel
2019-09-03 10:27 ` Ricardo Wurmus
2019-09-03 13:01 ` Ludovic Courtès
2019-09-03 13:48 ` P via Development of GNU Guix and the GNU System distribution.
2019-09-08 19:41 ` Ricardo Wurmus
2019-09-08 18:37 ` Hartmut Goebel
2019-09-08 19:08 ` Ricardo Wurmus [this message]
2019-09-10 8:42 ` Konrad Hinsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lfuy4ne7.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.