From: Ricardo Wurmus <rekado@elephly.net>
To: Brett Gilio <brettg@posteo.net>
Cc: Help Guix <help-guix@gnu.org>
Subject: Re: Using local package
Date: Tue, 13 Nov 2018 09:42:43 +0100 [thread overview]
Message-ID: <87r2fpv058.fsf@elephly.net> (raw)
In-Reply-To: <87ftw5igbs.fsf@posteo.net>
Hi Brett,
> I am wondering about a specific dilemma for developers. I know that I
> can run a specific guix environment container of sorts to hack on
> package code, but I am curious about how I could do about using that
> locally checked out code to build it and run it.
You can generate a tarball (e.g. with “make dist”) and then run
guix build the-package \
--with-source=the-tarball.tar.gz
“guix build” returns the store path to the newly built item. It won’t
result in a new generation of your profile. You can usually run the
software using the full store path.
--
Ricardo
prev parent reply other threads:[~2018-11-13 9:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 7:31 Using local package Brett Gilio
2018-11-13 8:42 ` Ricardo Wurmus [this message]
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=87r2fpv058.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=brettg@posteo.net \
--cc=help-guix@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.
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).