From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: How to reference external program used in shell-scripts?
Date: Tue, 3 Sep 2019 11:08:17 +0200 [thread overview]
Message-ID: <670e61cd-d3e3-6a91-0773-715d19f5052a@crazy-compilers.com> (raw)
In-Reply-To: <87d0hewwfu.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]
Hi Ricardo,
Am 09.08.19 um 10:54 schrieb Ricardo Wurmus:
> Whenever an input is changed the package will be rebuilt, because we
> can’t know if the presence of a package will affect the build or not.
>
> In the case of patching references the presence of the input *will*
> affect the output (as a reference to the absolute file name will be
> recorded). In the case of propagated inputs it’s really the same,
> expect that the package will also be installed into the target profile.
My concerns are not about building, but about installing. A concrete
example:
* Ansible is a Python program running ssh via a path to
/gnu/store/…-openssh-8.0p1/bin/ssh
* Mary installs ansible.
* Now openssh shows a serious bug and Mary updates openssh using "guix
-u openssh"
Obviously this will *not* update ansible, and ansible will still use the
old, vulnerable version of openssh.
OTOH, if ansible would run ssh via $PATH, ansible would pick up the new
version of openssh.
FWIW: some way to install openssh automatically along with ansible,
while not specifying a specific version of openssh to be used, thus if
openssh is updated (but ansible is not), ansible will pick up the new
version.
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
[-- Attachment #2: Type: text/html, Size: 2303 bytes --]
next prev parent reply other threads:[~2019-09-03 9: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 [this message]
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
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
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=670e61cd-d3e3-6a91-0773-715d19f5052a@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--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).