all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: unmush <unmush@proton.me>
Cc: 74609@debbugs.gnu.org
Subject: [bug#74609] [PATCH] Adding a fully-bootstrapped mono
Date: Fri, 13 Dec 2024 08:47:03 +0100	[thread overview]
Message-ID: <87ttb83tzc.fsf@gnu.org> (raw)
In-Reply-To: <iMoekcfwEfCp2uLTWzr-P2_OVyzTF-420AoXae5W6GK2kP5NvueOXBRzAIJBRN2U0c7Sl0HUzUy8eKWNuTs2uaiapCUkJUo5Ng9ahfsfGZ8=@proton.me> (unmush@proton.me's message of "Fri, 29 Nov 2024 15:05:09 +0000")

Hi,

unmush <unmush@proton.me> skribis:

> We used to have a mono package, but it was removed due to includingbootstrap binaries (among others).  This patch series introduces a full,
> 17-mono-package sequence that takes us from a mono-1.2.6 built fully
> from source to mono-6.12.0 built fully from source, using only packages
> that already have full bootstrap paths.  I make no promise that this is
> the shortest or most optimal path, but it exists and I have verified it
> works.
>
> As I've spent what is probably an unreasonable amount of time working
> toward this, I thought I'd share some of my thoughts, experiences, and
> commentary.  Sorry in advance if it gets a bit rambly or lecture-ish.

I join others in congratulating you!  This is very impressive, and a
great step forward.

I’ll make time to review and apply those patches if nobody beats me at it.

Thank you!

Ludo’.




  parent reply	other threads:[~2024-12-13  7:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-29 15:05 [bug#74609] [PATCH] Adding a fully-bootstrapped mono unmush via Guix-patches via
2024-12-05  6:21 ` Aaron Covrig via Guix-patches via
2024-12-05 22:07 ` Richard Sent
2024-12-13  7:47 ` Ludovic Courtès [this message]
2024-12-13 12:13   ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ttb83tzc.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=74609@debbugs.gnu.org \
    --cc=unmush@proton.me \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.