unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Andy Tai <atai@atai.org>
Cc: guix-devel@gnu.org
Subject: Re: bootstrapping scenario for a package
Date: Mon, 03 Jan 2022 15:37:06 +0100	[thread overview]
Message-ID: <87tuekkhrh.fsf@gnu.org> (raw)
In-Reply-To: <CAJsg1E85Ob1SptW4Ho7YkA6ptMxSAKX20D-JdocEiixpTmAi=A@mail.gmail.com> (Andy Tai's message of "Mon, 20 Dec 2021 12:06:01 -0800")

Hi!

Andy Tai <atai@atai.org> skribis:

> Hi, I was trying to update mono to the current release version.  The
> build step as documented actually says to download a minimal C#
> compiler from the mono site which is then used to compile the rest of
> the source to build the full system.   I looked and did not find the
> source of this minimal compiler--so it is a black box in a way.
>
> In free software it is ideal to build everything from source.   I
> wonder how is such a package handled in Guix?   What is the strategy
> for bootstrapping?   Thanks

In several important cases (GCC, Java, Rust, OCaml, etc.), Guix goes to
great lengths to build things from source.  Most of the time, that
involves doing work that upstream isn’t doing, such as finding a path
from older or separate implementations that can be built from source to
the target compiler.  You can read a bit about it here:

  https://guix.gnu.org/en/blog/tags/bootstrapping/

What you describe for Mono sounds problematic.  If would be nice to see
if the currently packaged version already had this problem, and if not,
we could make it a dependency of the new version.

HTH!

Ludo’.


      reply	other threads:[~2022-01-03 14:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-20 20:06 bootstrapping scenario for a package Andy Tai
2022-01-03 14:37 ` Ludovic Courtès [this message]

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=87tuekkhrh.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=atai@atai.org \
    --cc=guix-devel@gnu.org \
    /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).