all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Suhail Singh <suhailsingh247@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Suhail Singh <suhailsingh247@gmail.com>,
	 Daniel Littlewood <danielittlewood@gmail.com>,
	 Evan Cooney <evancooney71@gmail.com>,
	guix-devel <guix-devel@gnu.org>
Subject: Re: Including code in a non-Guile language into Guix
Date: Thu, 31 Oct 2024 13:12:15 -0400	[thread overview]
Message-ID: <87plngb3io.fsf@gmail.com> (raw)
In-Reply-To: <874j4smesp.fsf@elephly.net> (Ricardo Wurmus's message of "Thu, 31 Oct 2024 17:13:10 +0100")

Ricardo Wurmus <rekado@elephly.net> writes:

>>> guix pull ("38k new commits"): 21m45s
>>> guix pull immediately after: 2m25s
>>> ...
>>>
>>> nix-channel --update: 0m23s
>>
>> Those are some interesting comparisons.  Is the reason guix pull takes
>> so long as compared to updating nix-channel primarily due to the
>> authentication of commits?  Or something else?
>
> It's "something else".  This is a comparison between apples and
> giraffes.  "guix pull" does a different job than "nix-channel"; the
> latter only needs to download a new version of inert data whereas the
> former computes a trampoline and then updates Guix itself.
>
> The fundamental difference is that Guix is a library, not merely
> "package metadata" that would be independent of the Guix executable.

Thank you for that explanation.

-- 
Suhail


  reply	other threads:[~2024-10-31 17:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-31  2:34 Including code in a non-Guile language into Guix Evan Cooney
2024-10-31 12:31 ` Daniel Littlewood
2024-10-31 14:15   ` Suhail Singh
2024-10-31 16:13     ` Ricardo Wurmus
2024-10-31 17:12       ` Suhail Singh [this message]
2024-10-31 16:15     ` Runciter via Development of GNU Guix and the GNU System distribution.
2024-10-31 16:23       ` Evan Cooney
2024-10-31 16:15 ` Ricardo Wurmus

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87plngb3io.fsf@gmail.com \
    --to=suhailsingh247@gmail.com \
    --cc=danielittlewood@gmail.com \
    --cc=evancooney71@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.