unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: John Soo <jsoo1@asu.edu>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Single channel update (or channels vs. GUIX_PACKAGE_PATH)
Date: Mon, 4 Feb 2019 15:24:19 -0800	[thread overview]
Message-ID: <15ACA13D-35AC-4896-90DD-6377250E4624@asu.edu> (raw)
In-Reply-To: <87r2cn6t66.fsf@ambrevar.xyz>

Hello Pierre,

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>

To test runtime behavior I still have to pull which does mean pulling the default channel, too.  This so far has worked well. If pulling becomes too much, maybe specifying a commit of the default guix channel could work. What do you think?

- John



> On Feb 4, 2019, at 3:16 PM, Pierre Neidhardt <mail@ambrevar.xyz> wrote:
> 
> Hi again :)
> 
> I was discussing "channels in practice" with Zimoun and we were asking
> ourselves: Can we pull a specific channel without pulling
> %default-channels?
> 
> If not, is there a convenient way to edit+test the package definitions
> in local channels?
> 
> Maybe I'm missing the obvious?
> 
> --
> Pierre Neidhardt
> https://ambrevar.xyz/

  reply	other threads:[~2019-02-04 23:24 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 [this message]
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

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=15ACA13D-35AC-4896-90DD-6377250E4624@asu.edu \
    --to=jsoo1@asu.edu \
    --cc=help-guix@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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).