From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Carlo Zancanaro <carlozancanaro@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Building from a local source code checkout
Date: Thu, 21 Dec 2017 07:38:53 +0100 [thread overview]
Message-ID: <m1vah0d1qa.fsf@ordinateur-de-catherine--konrad.home> (raw)
In-Reply-To: <BBE14C04-5320-4439-8AE9-00B4AC19BB7D@gmail.com>
Hi Carlo,
> On 20 December 2017 9:19:00 pm AEDT, Konrad Hinsen <konrad.hinsen@fastmail.net> wrote:
>> > guix build python-activepapers
>>--with-source=~/Development/python-activepaper
>>guix build: error: lstat: No such file or directory:
>>"~/Development/python-activepapers"
>
> I found earlier today that the tilde wasn't expanded in guix package
> --manifest. Maybe it's the same for --with-source. Try putting your
> home directory in as an absolute path.
Oops, you are right! So
guix build python-activepapers --with-source=$HOME/Development/python-activepapers/
actually works, but
guix build python-activepapers --with-source=$HOME/Development/python-activepapers
(without the terminating slash) doesn't:
guix build: error: guix/scripts/build.scm:155:6: package
`python-activepapers-0.2.2' has an invalid input: ("source"
"/gnu/store/bbi86dn5nq6f79lhvs7ghzisjahjaq5p-python-activepapers")
Perhaps I should stop trying to understand computers ;-)
Thanks,
Konrad.
next prev parent reply other threads:[~2017-12-21 6:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 11:34 Building from a local source code checkout Konrad Hinsen
2017-12-19 17:15 ` Ludovic Courtès
2017-12-20 8:52 ` Konrad Hinsen
2017-12-20 10:19 ` Konrad Hinsen
2017-12-20 12:41 ` Carlo Zancanaro
2017-12-21 6:38 ` Konrad Hinsen [this message]
2017-12-21 10:38 ` Pjotr Prins
2017-12-21 11:20 ` Martin Castillo
2017-12-21 14:38 ` Ludovic Courtès
2017-12-21 16:53 ` Martin Castillo
2017-12-22 9:29 ` Ludovic Courtès
2017-12-21 17:02 ` Konrad Hinsen
2017-12-22 23:07 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1vah0d1qa.fsf@ordinateur-de-catherine--konrad.home \
--to=konrad.hinsen@fastmail.net \
--cc=carlozancanaro@gmail.com \
--cc=guix-devel@gnu.org \
/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.