From: Andreas Enge <andreas@enge.fr>
To: "André A. Gomes" <andremegafone@gmail.com>
Cc: Nigko Yerden <nigko.yerden@gmail.com>, help-guix@gnu.org
Subject: Re: No 'guix pull' substitutes for foreign distros?
Date: Sun, 19 May 2024 22:17:45 +0200 [thread overview]
Message-ID: <ZkpeaS3iBuEnUCFo@jurong> (raw)
In-Reply-To: <87zfslr3rf.fsf@gmail.com>
Am Sun, May 19, 2024 at 10:38:28PM +0300 schrieb André A. Gomes:
> Nigko Yerden <nigko.yerden@gmail.com> writes:
> > Hello Guix!
> > Shouldn't 'guix pull' substitutes also work on foreign distros?
> I'd like to re-iterate the question. I have been using the Guix system
> for years but lately I'm also using it as a package manager. It is
> rather off-putting that guix pull will take more than 20 minutes in this
> setting. Newcomers will probably start by using it a package manager
> and only then commit to the system.
I have no answer, but can confirm the problem and state that it is not
related to using Guix as a package manager or as a full system. In both
cases "guix pull" should do the same thing.
However, I am also surprised by the following behaviour: I have three users
on my Guix system, and always do three "guix pull --commit=..." on the same
commit for all of them. It happens that the second or third user compiles
derivations that I would expect to be in the store already. I do not know
what the differences are. Someone suggested to me it could be related to
channels. Apparently, using a different set of channels leads to different
derivations. But last week it has also happened for my two users with only
the main channel.
Andreas
next prev parent reply other threads:[~2024-05-19 20:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 15:53 No 'guix pull' substitutes for foreign distros? Nigko Yerden
2024-05-19 19:38 ` André A. Gomes
2024-05-19 20:17 ` Andreas Enge [this message]
2024-05-19 23:42 ` pelzflorian (Florian Pelz)
2024-05-21 9:14 ` André A. Gomes
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=ZkpeaS3iBuEnUCFo@jurong \
--to=andreas@enge.fr \
--cc=andremegafone@gmail.com \
--cc=help-guix@gnu.org \
--cc=nigko.yerden@gmail.com \
/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).