unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Andreas Reuleaux <rx@a-rx.info>
To: help-guix <help-guix@gnu.org>
Subject: Re: pulling from my personal channel only - is this possible ?
Date: Wed, 01 Sep 2021 23:15:20 +0100	[thread overview]
Message-ID: <87sfyovt6v.fsf@softland> (raw)
In-Reply-To: <ygu1r68uhcd.fsf@netpanic.org> (Simon Streit's message of "Wed, 01 Sep 2021 23:16:34 +0200")

Hm - maybe I did not make myself clear [?]. Ideally I would have
something like this (I am exaggerating):

./channels.scm 
--8<---------------cut here---------------start------------->8---
(cons (channel
       (name 'my-stuff)
       (url "git://git.a-rx.info/channel")
       (introduction
        (make-channel-introduction
         "..."
         (openpgp-fingerprint
          "...")
         ))

       )

      ;; tata !!
      %default-channels-dont-bother-pulling-but-use-as-from-last-pull-and-already-on-my-computer
  )
--8<---------------cut here---------------end--------------->8---


I.e. while developing (and pulling from my own channel frequently):
don't spend 53s each time, and then - once in a while - pull from both channels.



Thanks,
  -A


Simon Streit <lists@netpanic.org> writes:

> Hi Andreas,
>
> Andreas Reuleaux <rx@a-rx.info> writes:
>> While working on those packages, I often do a
>>
>> guix pull
>
> Hey, do you just want to pull, say, from your own channel, but not Guix'
> default?  This is something I just figured out a couple of days ago!
>
> One way, and this is only one possibility, is to modify your
> channels.scm in such a way that you directly pin your channels to the
> commit, or if necessary, a branch, and basically pull whatever you want
> to get your newest fix.
>
> This is how my channels.scm more or less looks like at the moment:
>
> (use-modules (guix ci))
> (list (channel-with-substitutes-available
>        %default-guix-channel
>        "https://ci.guix.gnu.org"))
> (list
>  (channel
>   (name 'guix)
>   (url "https://git.savannah.gnu.org/git/guix.git")
>   ;; (branch "master")
>   (commit "a8dd285d5a0670abf124a721e6ba94da045b24ba")
>   (introduction
>    (make-channel-introduction
>     "9edb3f66fd807b096b48283debdcddccfea34bad"
>     (openpgp-fingerprint
>      "BBB0 2DDF 2CEA F6A8 0D1D  E643 A2A0 6DF2 A33A 54FA"))))
>  (channel
>   (name 'hacks)
>   (url "http://example.com/hacks.git")
>   (branch "master")
>   (commit "e3fd7d9e4aa541f63133c4678f316b5239364c34")))
>
> Be aware, that the downside is that anytime you want to go further, you
> have to comment things out again, or go back to the default definition. 
>
>
> Kind regards
> Simon


  parent reply	other threads:[~2021-09-01 22:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-01 15:59 pulling from my personal channel only - is this possible ? Andreas Reuleaux
2021-09-01 16:53 ` raingloom
2021-09-01 19:44   ` Andreas Reuleaux
2021-09-01 21:57     ` raingloom
2021-09-01 22:16       ` Andreas Reuleaux
2021-09-01 21:16 ` Simon Streit
2021-09-01 21:43   ` Andreas Reuleaux
2021-09-01 23:26     ` Andreas Reuleaux
2021-09-02  8:33       ` Simon Streit
2021-09-01 22:15   ` Andreas Reuleaux [this message]
2021-09-02 11:29 ` zimoun
2021-09-02 11:43   ` Andreas Reuleaux
2021-09-02 20:06     ` zimoun

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=87sfyovt6v.fsf@softland \
    --to=rx@a-rx.info \
    --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).