From: zimoun <zimon.toutoune@gmail.com>
To: Phil <phil@beadling.co.uk>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: guix pull only from private channel
Date: Tue, 22 Dec 2020 12:44:09 +0100 [thread overview]
Message-ID: <86im8u83qu.fsf@gmail.com> (raw)
In-Reply-To: <858s9qxkah.fsf@beadling.co.uk>
Hi,
On Tue, 22 Dec 2020 at 09:27, Phil <phil@beadling.co.uk> wrote:
> Yep this is what I've ended up doing - but am still a bit surprised that
> even with a pinned guix commit id, and a private channel containing a
> single trivial package with available substitute, doing a 'git pull' is
> still fairly expensive (approx 1min). This is quicker than pulling
> latest guix, of course - so there is some improvement.
I agree. Some optimizations could be done, maybe by cutting some
unnecessary computations or check.
> Personally I think GUIX_PACKAGE_PATH still serves some practical
> purpose, which is not as well covered by channels?
Personally, I do not use GUIX_PACKAGE_PATH for local packages but the
option ’--load-path’ when I need it.
All the best,
simon
prev parent reply other threads:[~2020-12-22 11:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 17:58 guix pull only from private channel Phil
2020-12-16 14:07 ` zimoun
2020-12-19 12:28 ` Phil
2020-12-21 12:16 ` zimoun
2020-12-22 9:27 ` Phil
2020-12-22 11:44 ` zimoun [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=86im8u83qu.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=phil@beadling.co.uk \
/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).