unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Simon Streit <lists@netpanic.org>
To: Andreas Reuleaux <rx@a-rx.info>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: pulling from my personal channel only - is this possible ?
Date: Thu, 02 Sep 2021 10:33:23 +0200	[thread overview]
Message-ID: <ygupmtrtm0c.fsf@netpanic.org> (raw)
In-Reply-To: <87a6kvubbm.fsf@softland> (Andreas Reuleaux's message of "Thu, 02 Sep 2021 00:26:37 +0100")

Andreas Reuleaux <rx@a-rx.info> writes:
> OK, once more: I am beginning to understand your idea:
>
> you are fixing the guix core channel to a specific commit:
> "9edb3f66fd807b096b48283debdcddccfea34bad" here, i.e. from Saturday,
> Aug 28 2021

Yes, the channel is fixed and thus not pulled.

> Maybe it is not the pulling itself that is so expensive, but
> "Computing the Guix derivation..." (that is part of the pull command
> as well apparently) ?
>
> Is it necessary to always have a complete Guix derivation built, when
> I just want to update my system with some changes of my own?

Yes, as far as I understand, for any pull a new derivation has to be
built to reflect any change, but only as long as a commit has changed,
and as a result of any package definition being modified.  This is an
inherent design of Guix, that derivations ought to be built.  Someone
better correct me on this statement.  Changes are that I didn't get it
right. There is more to read about it, and substantial work is been done
to reduce build times. [1] [2]

[1] https://guix.gnu.org/manual/en/html_node/Derivations.html
[2] https://guix.gnu.org/en/blog/2021/building-derivations-how-complicated-can-it-be/

> Summary line: I guess I am beginning to understand your idea, but it
> practice it does not make a difference, as each pull still takes more
> then 50sec.

It might not, but it might help that while you are developing on your own
channel, you do not want to surprisingly upgrade your profile because
Guix' main channel pushed an update in the mean time.  That can cost a
lot of space, and more time and also, say, even a dependency on your
package could change too.

Yes, I've noticed that all pulls take time.  There's a reason why I keep
my old laptop at certain commits for longer periods now.  It simply
dosn't have the resources to do this.  I do all the tricks -- offloading,
package sharing -- to speed up the upgrade process.

While looking around, supplying your package definitions from a file
that can be found in within ‘GUIX_PACKAGE_PATH’ [3] gives you the
ability to pass on packages that do not need to be part of any channel.

[3] https://guix.gnu.org/en/cookbook/en/html_node/GUIX_005fPACKAGE_005fPATH.html#GUIX_005fPACKAGE_005fPATH


Regards


  reply	other threads:[~2021-09-02  8:33 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 [this message]
2021-09-01 22:15   ` Andreas Reuleaux
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=ygupmtrtm0c.fsf@netpanic.org \
    --to=lists@netpanic.org \
    --cc=help-guix@gnu.org \
    --cc=rx@a-rx.info \
    /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).