From: zimoun <zimon.toutoune@gmail.com>
To: Jesse Gibbons <jgibbons2357@gmail.com>, help-guix@gnu.org
Subject: Re: Am I using --with-source improperly?
Date: Thu, 27 Aug 2020 10:38:20 +0200 [thread overview]
Message-ID: <86o8mweb5v.fsf@gmail.com> (raw)
In-Reply-To: <15c6eb6d-fb0f-dfc4-c8a2-07fff50c12c8@gmail.com>
Dear,
On Wed, 26 Aug 2020 at 20:34, Jesse Gibbons <jgibbons2357@gmail.com> wrote:
> I asked about this on the IRC but had no luck.
>
> IIUC --with-source=package=source should set the source for "package" to
> "source" when something being built depends on "package". For example,
> `guix build --with-soure=python2=/tmp/python2 lci` should build the lci
> with the python2 source in /tmp/python2, and should work because python2
> is a dependency of lci. However, when I try that, I get the message
> "guix build: warning: transformation 'with-source' had no effect on
> lci@0.11.2". Am I using the --with-source option incorrectly, or is this
> some sort of bug? I replace "--with-source=python2=/tmp/python2" with
> "--with-source=lci=/tmp/python2" when /tmp/python2 doesn't even exist,
> and it gives me the result I would expect: 'guix build: error: lstat: No
> such file or directory: "/tmp/python2"'
>
> Should I file this as a bug report?
Instead, maybe “--with-source=python-2=/tmp/python2“?
BTW, note that for more complex examples, the complete graph of
dependencies would not be rewritten (if I read correctly). That’s the
job of ‘package-with-explicit-python’ and especially
‘package-with-python2’.
Hope that helps.
simon
next prev parent reply other threads:[~2020-08-27 8:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 2:34 Am I using --with-source improperly? Jesse Gibbons
2020-08-27 8:38 ` zimoun [this message]
2020-08-27 11:23 ` Carlo Zancanaro
2020-08-27 16:07 ` Jesse Gibbons
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=86o8mweb5v.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=jgibbons2357@gmail.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.
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).