unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: 27865@debbugs.gnu.org
Subject: [bug#27865] [PATCH 0/3] Use Guile-Git for 'guix pull'
Date: Fri, 28 Jul 2017 22:28:14 +0200	[thread overview]
Message-ID: <20170728202814.5355-1-ludo@gnu.org> (raw)

Hello Guix!

This is the long-awaited change where ‘guix pull’ fetches code over Git
instead of stupidly grabbing a full snapshot generated on-the-fly by the
poor Savannah servers.

As a side-effect, ‘guix pull’ gains a ‘--commit’ and a ‘--branch’
option.  Also, ‘guix --version’ will now show a Git commit ID instead of
a date.

This change makes Guile-Git a hard dependency.  The transition might be
somewhat bumpy since it’s possible that users not having Guile-Git
installed will run ‘guix pull’ and, upon completion, will get an error
when they re-run ‘guix pull’.  This will be fixed by installing
‘guile-git’.  Thinking about it, (guix scripts pull) could perhaps try
to be smart and have an error message saying “please install Guile-Git”
or something.

Thoughts?

Another (minor) issue is that there hasn’t been an official release of
Guile-Git yet, and things are still changing a little bit.  However I
think most of the important things are in place.

Guile-Git currently lacks bindings for the progress-report API when
cloning the repo.  We’ll use it when it’s available.

Feedback welcome!

Thanks,
Ludo’.

Ludovic Courtès (3):
  build: Make Guile-Git a hard requirement.
  pull: Fetch source code from Git.
  pull: Use the commit ID as the version string.

 Makefile.am           |   8 +-
 configure.ac          |  10 ++-
 doc/guix.texi         |  29 ++++---
 guix/scripts/pull.scm | 219 ++++++++++++++++++++++++--------------------------
 4 files changed, 124 insertions(+), 142 deletions(-)

-- 
2.13.3

             reply	other threads:[~2017-07-28 20:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-28 20:28 Ludovic Courtès [this message]
2017-07-28 20:45 ` [bug#27865] [PATCH 1/3] build: Make Guile-Git a hard requirement Ludovic Courtès
2017-07-28 20:45   ` [bug#27865] [PATCH 2/3] pull: Fetch source code from Git Ludovic Courtès
2017-07-30 13:15     ` Mathieu Othacehe
2017-07-30 20:38       ` Ludovic Courtès
2017-07-31  9:09         ` Mathieu Othacehe
2017-07-31 13:40           ` Ludovic Courtès
2017-07-31 13:56             ` Mathieu Othacehe
2017-07-28 20:45   ` [bug#27865] [PATCH 3/3] pull: Use the commit ID as the version string Ludovic Courtès
2017-07-31 15:25 ` [bug#27865] [PATCH 0/3] Use Guile-Git for 'guix pull' Ludovic Courtès
2017-08-01 22:10   ` bug#27865: " Ludovic Courtès

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=20170728202814.5355-1-ludo@gnu.org \
    --to=ludo@gnu.org \
    --cc=27865@debbugs.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.
Code repositories for project(s) associated with this public inbox

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

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).