From: Chris Marusich <cmmarusich@gmail.com>
To: John Soo <jsoo1@asu.edu>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Single channel update (or channels vs. GUIX_PACKAGE_PATH)
Date: Sat, 09 Feb 2019 00:43:25 -0800 [thread overview]
Message-ID: <87o97l73o2.fsf@gmail.com> (raw)
In-Reply-To: <15ACA13D-35AC-4896-90DD-6377250E4624@asu.edu> (John Soo's message of "Mon, 4 Feb 2019 15:24:19 -0800")
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]
John Soo <jsoo1@asu.edu> writes:
> I’ve been working a lot on some packages in a private channels and my
> workflow is usually focused on building properly which is a matter of:
>
> guix build -L /path/to/channel <package>
FYI, I believe you can also specify local paths in the channel
description file, itself, either by saying "file:///path/to/channel" or
"/path/to/channel" - I can't remember which.
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2019-02-09 8:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 23:16 Single channel update (or channels vs. GUIX_PACKAGE_PATH) Pierre Neidhardt
2019-02-04 23:24 ` John Soo
2019-02-05 17:52 ` Pierre Neidhardt
2019-02-05 20:02 ` Ricardo Wurmus
2019-02-05 20:45 ` Pierre Neidhardt
2019-02-12 16:36 ` Ludovic Courtès
2019-02-12 17:26 ` Pierre Neidhardt
2019-02-09 8:43 ` Chris Marusich [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=87o97l73o2.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=help-guix@gnu.org \
--cc=jsoo1@asu.edu \
/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).