unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>
To: Paul Dufresne <dufresnep@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: How/When will guix pull stop to compile the 616 files?
Date: Tue, 08 Aug 2017 09:50:39 +0200	[thread overview]
Message-ID: <8760dy8pm8.fsf@gmail.com> (raw)
In-Reply-To: <CAGQ-=q0gYVQ2LoiRnMfYWew37vibi2OcVTLx7zqN_6GdLcgANg@mail.gmail.com>

Hi Paul

Paul Dufresne writes:

> Ok, I was able to make a guix pull without compiling the 616 files.
>
> But I just done it again, and it seems to compile the full 616 files
> each time a commit is done...
> I think.

This is right — guix pull will download (now via git) the latest
available snapshot.  If that snapshot is identical to your current
snapshot, it will not compile anything, otherwise it will do a full
installation, which involves compiling all project files.

New snapshots are indeed created by people commiting to master.

Now that guix pull uses a git backend, it might be possible to move
towards a model whereby pull only recompiles files affected by the
missing commits (that would be leaves that have been changed, or the
file thas has been changed and all its dependents).  But that's me
speculating, not volunteering unfortunately…

HTH,

Alex

  reply	other threads:[~2017-08-08  7:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-08  0:59 How/When will guix pull stop to compile the 616 files? Paul Dufresne
2017-08-08  1:43 ` Paul Dufresne
2017-08-08  7:50   ` Alex Sassmannshausen [this message]
2017-08-08 13:02     ` Paul Dufresne
2017-08-08 20:23       ` Ricardo Wurmus
2017-08-08 20:39         ` Jack Hill
2017-08-09  5:43           ` Paul Dufresne
2017-08-09  8:08           ` Ricardo Wurmus
2017-08-09 13:41             ` Jack Hill
2017-08-13  3:21       ` Quiliro Ordonez Baca

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=8760dy8pm8.fsf@gmail.com \
    --to=alex.sassmannshausen@gmail.com \
    --cc=dufresnep@gmail.com \
    --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).