unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: guix-devel@gnu.org,
	Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>,
	Vivien Kraus <vivien@planete-kraus.eu>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Bootstrap a GNU source distribution from git
Date: Tue, 01 Oct 2024 10:20:54 +0000	[thread overview]
Message-ID: <9DD4B472-70C8-489F-B86E-23891365E9C6@tobias.gr> (raw)
In-Reply-To: <20240930234306.1609bf7a@primary_laptop>

Hi Denis,

On 30 September 2024 21:43:06 UTC, Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> wrote:
> what is Guix policy with
>regard to source code when there are multiple providers (typically git
>vs tarball)?

There's never been an explicit policy as far as I'm aware.

In the past decade the consensus has shifted from release tarballs towards both, tarballs and VCS repository checkouts, as long as they represent an upstream release.

For the reasons you point out, I expect the tides to shift further in favour of VCS checkouts as time moves on.  I'm in favour of this.

If you're interested in formalising this 'policy', it would be a good test of this 'RFC' business that's seen little use so far.

>Since Guix also checks the hash of the source code an idea to improve
>things could also be to modify Guix to allow the use of external tools
>to bootstrap the download of source code through version control and
>for instance download git from git.

I don't understand what you mean by this, or what 'modify Guix' means and why it would be needed?



Kind regards,

T G-R

Sent on the go.  Excuse or enjoy my brevity.


  reply	other threads:[~2024-10-01 15:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-29 17:52 Bootstrap a GNU source distribution from git Vivien Kraus
2024-09-30 21:43 ` Denis 'GNUtoo' Carikli
2024-10-01 10:20   ` Tobias Geerinckx-Rice [this message]
2024-10-05 22:57     ` Denis 'GNUtoo' Carikli
2024-10-06  7:50 ` Janneke Nieuwenhuizen

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=9DD4B472-70C8-489F-B86E-23891365E9C6@tobias.gr \
    --to=me@tobias.gr \
    --cc=GNUtoo@cyberdimension.org \
    --cc=guix-devel@gnu.org \
    --cc=vivien@planete-kraus.eu \
    /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).