unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Sharlatan Hellseher <sharlatanus@gmail.com>
Cc: "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: Sun, 10 Nov 2024 20:40:05 +0900	[thread overview]
Message-ID: <87r07jwc4q.fsf@gmail.com> (raw)
In-Reply-To: <CAO+9K5oYYsrhHi+mvC+ow0ks+PV_2Ej9AkKMQ3Djj9_KehCewQ@mail.gmail.com> (Sharlatan Hellseher's message of "Wed, 30 Oct 2024 09:12:49 +0000")

Hi again,

Sharlatan Hellseher <sharlatanus@gmail.com> writes:

> Hi,
>
> Thank you for the patch.
>
> Cc core team
>
> We may blow the dust from this <https://issues.guix.gnu.org/44926> as well
> and come to some consensus.

For the record, I think #44926 could be considered; it packages a
non-public bootstrap dart (which is the same as this submission --
pulling binaries from the net), but then goes on to rebuild itself using
that.

I think we have other compilers in that situation packaged in Guix
(though I forget which ones).

Do we have a definitive policy on this?  If we do, I'm missing where
it's laid out clearly.  If we don't should we author one?  What would be
the big lines of what it says?

CC-ing co-maintainers.

-- 
Thanks,
Maxim




  reply	other threads:[~2024-11-10 12:07 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 [this message]
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
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=87r07jwc4q.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=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).