unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: 01/02: gnu: fmt: Use HTTPS and git-fetch.
Date: Wed, 11 Mar 2020 15:39:39 +0100	[thread overview]
Message-ID: <87tv2vgdlg.fsf@gnu.org> (raw)
In-Reply-To: <87lfodl6u5.fsf@devup.no> (Marius Bakke's message of "Fri, 06 Mar 2020 18:40:50 +0100")

Hi!

Marius Bakke <mbakke@fastmail.com> skribis:

> Pierre Neidhardt <mail@ambrevar.xyz> writes:
>
>> Duh, I confused these with the github generated archive, sorry about
>> that.
>>
>> Is there any preference between git-fetch and url-fetch?
>
> url-fetch requires less bandwidth, and does not depend on 'git'.
>
> Though the most important distinction is that uploaded releases
> sometimes contain pre-processed sources (e.g. documentation) that need
> additional dependencies or scripts when building from the raw repository
> (this is why you often need to add autoconf, libtool & friends as inputs
> when building Autotools projects from git).
>
> I don't know whether there is a difference between the uploaded fmt
> zipball and the git repository.

Other considerations:

  - Bandwidth requirement for source code downloads has never been a
    criterion so far.

  - Git references are nice because they’re (roughly) content-addressed.

  - ‘guix lint -c archival’ archives Git references on Software
    Heritage; it does not archive tarballs (though SWH will do it
    for us eventually.)

Ludo’.

  parent reply	other threads:[~2020-03-11 14:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200306091524.5044.11103@vcs0.savannah.gnu.org>
     [not found] ` <20200306091525.E8A1621163@vcs0.savannah.gnu.org>
2020-03-06 14:37   ` 01/02: gnu: fmt: Use HTTPS and git-fetch Marius Bakke
2020-03-06 15:07     ` Pierre Neidhardt
2020-03-06 17:40       ` Marius Bakke
2020-03-07  7:46         ` Pierre Neidhardt
2020-03-07 11:37           ` Pierre Neidhardt
2020-03-11 14:39         ` Ludovic Courtès [this message]
2020-03-11 14:54           ` Pierre Neidhardt
2020-05-13  1:08             ` best practise between git-fetch vs url-fetch? zimoun
2020-05-13  8:24               ` Brice Waegeneire
2020-05-13 18:07                 ` Tobias Geerinckx-Rice
2020-05-14 16:16                   ` Jack Hill
2020-05-24 20:04                     ` Josh Marshall
2020-05-24 20:30                     ` Ludovic Courtès
2020-05-25  4:54                       ` Jack Hill
2020-05-25 21:17                         ` Ludovic Courtès
2020-05-26  2:05                           ` Jack Hill
2020-05-13 17:13               ` Leo Famulari
2020-05-24 20:34                 ` Ludovic Courtès
2020-05-26 11:41               ` 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=87tv2vgdlg.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mbakke@fastmail.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.
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).