From: Nicolas Graves via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: Adam Faiz <adam.faiz@disroot.org>
Cc: guix-devel@gnu.org, Timothy Sample <samplet@ngyro.com>
Subject: Re: Guidelines for bootstrapping with lots of inputs
Date: Tue, 20 Feb 2024 16:35:29 +0100 [thread overview]
Message-ID: <87v86jf8se.fsf@ngraves.fr> (raw)
In-Reply-To: <5AAC67F6-C1C2-407D-B7CA-882C8F9568EA@disroot.org>
On 2024-02-20 15:11, Adam Faiz wrote:
>> WDYT? Are there guidelines somewhere about how to do proper bootstrapping in these cases where hundreds of packages are involved?
>
> Not really, but your idea to rewrite inputs for the bootstrapping process does simplify things a lot.
>
> How is typescript bootstrapped? Even though you'll have to repeat the trial and error process again, I think using sucrase is easier for bootstrapping typescript: https://lists.gnu.org/archive/html/guix-devel/2024-02/msg00122.html
Timothy claimed that building typescript with esbuild has been done (by
singpolyma) in guixrus and it indeed seems it is.
https://lists.gnu.org/archive/html/guix-devel/2024-02/msg00123.html
https://git.sr.ht/~whereiseveryone/guixrus/tree/master/item/guixrus/packages/javascript/typescript.scm
What I've done currently is to bootstrap tape (but not all packages
using tape as a native-input in the process). The idea is to build tap
and typescript from there.
--
Best regards,
Nicolas Graves
next prev parent reply other threads:[~2024-02-20 15:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 15:11 Guidelines for bootstrapping with lots of inputs Adam Faiz
2024-02-20 15:21 ` Adam Faiz
2024-02-20 15:35 ` Nicolas Graves via Development of GNU Guix and the GNU System distribution. [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-20 11:00 Nicolas Graves via Development of GNU Guix and the GNU System distribution.
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=87v86jf8se.fsf@ngraves.fr \
--to=guix-devel@gnu.org \
--cc=adam.faiz@disroot.org \
--cc=ngraves@ngraves.fr \
--cc=samplet@ngyro.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).