unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: "Sharlatan Hellseher" <sharlatanus@gmail.com>,
	"GNU Guix maintainers" <guix-maintainers@gnu.org>,
	zimoun <zimon.toutoune@gmail.com>,
	"Ludovic Courtès" <ludo@gnu.org>,
	"Efraim Flashner" <efraim@flashner.co.il>,
	"Andreas Enge" <andreas@enge.fr>,
	74078@debbugs.gnu.org
Subject: [bug#74078] [PATCH] gnu: Add dart
Date: Tue, 12 Nov 2024 22:03:41 +0900	[thread overview]
Message-ID: <874j4c38pe.fsf@gmail.com> (raw)
In-Reply-To: <872BA542-08F9-4F30-AACE-F5669BF2EC5D@tobias.gr> (Tobias Geerinckx-Rice's message of "Sun, 10 Nov 2024 18:04:49 +0000")

Hi Tobias,

Tobias Geerinckx-Rice <me@tobias.gr> writes:

> On 10 November 2024 17:47:59 UTC, Tobias Geerinckx-Rice <me@tobias.gr> wrote:
>>We could keep the sky from falling by documenting that once a known bootstrap path exists, it *must* be used.
>
> As well as mandating the oldest (which is almost certainly the
> smallest) known binary seed.  And we must count it as such.
>
> Granted, it'll ruin our ‘binary seed reduced by N MiB!’ blog posts in
> exchange for a larger/more modern package collection.

I'm pretty sure we already have some binary bootstrapped compilers.
Your suggestions toward documenting a policy make a lot of sense to me;
if you have the bandwidth, I'd like to see it drafted, perhaps as an RFC?

-- 
Thanks,
Maxim




  reply	other threads:[~2024-11-12 13:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-28 20:45 [bug#74078] [PATCH] gnu: Add dart Jørgen Kvalsvik
2024-10-30  9:12 ` Sharlatan Hellseher
2024-11-10 11:40   ` Maxim Cournoyer
2024-11-10 17:47     ` Tobias Geerinckx-Rice via Guix-patches via
2024-11-10 18:04       ` Tobias Geerinckx-Rice via Guix-patches via
2024-11-12 13:03         ` Maxim Cournoyer [this message]
2024-11-05  5:20 ` bug#74078: " Maxim Cournoyer
2024-11-05  7:30   ` [bug#74078] " Jørgen Kvalsvik

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=874j4c38pe.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=74078@debbugs.gnu.org \
    --cc=andreas@enge.fr \
    --cc=efraim@flashner.co.il \
    --cc=guix-maintainers@gnu.org \
    --cc=ludo@gnu.org \
    --cc=me@tobias.gr \
    --cc=sharlatanus@gmail.com \
    --cc=zimon.toutoune@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. 
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).