unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "jgart" <jgart@dismail.de>
To: guix-devel@gnu.org
Cc: rprior@protonmail.com, mail@davie.li,
	"Raghav Gururajan" <rg@raghavgururajan.name>,
	"Pjotr Prins" <pjotr2020@thebird.nl>,
	"Bonface Munyoki K." <me@bonfacemunyoki.com>,
	"John Soo" <jsoo1@asu.edu>
Subject: Crystal Bootstrapping Journey
Date: Mon, 21 Jun 2021 16:33:56 +0000	[thread overview]
Message-ID: <cebce81e56dcb7a5f9be0229f2a4ca73@dismail.de> (raw)

Hi Guix,

We've (Ryan, David, Raghav, and others) started packaging crystal for guix: https://crystal-lang.org/

See 49142 and 49158 in the issue tracker.

Here are some notes, questions, and a list of dependencies regarding what is needed to finish a properly bootstraped crystal package:

https://github.com/ryanprior/guix-packages/blob/master/testing/crystal.org

We are trying to recreate this bootstrapping process:

https://github.com/crystal-lang/bootstrap-script

There are 160 stages!

A few questions extracted from the notes follow:

Is it preferable to have 160 bootstrap packages, one for each stage, or one big bootstrap package with 160 build-* stages, or somewhere inbetween?

Each stage needs a different checkout of the git repository - can we preserve info in .git such that we can checkout again during the build, or do we want to have each checkout be an independent input to the package?

How best can we use Guile macros to clean up the large amount of code implied by executing 160 stages of bootstrap logic?

best regards,

jgart

ps If you'd like to discuss more and help us in this effort reply here and/or come join us this Saturday for another guix packaging meetup:

https://events.nixnet.services/events/11610807-dd89-47e7-bd6c-64429e48e338


             reply	other threads:[~2021-06-21 17:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-21 16:33 jgart [this message]
2021-06-21 19:40 ` Crystal Bootstrapping Journey Leo Prikler

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=cebce81e56dcb7a5f9be0229f2a4ca73@dismail.de \
    --to=jgart@dismail.de \
    --cc=guix-devel@gnu.org \
    --cc=jsoo1@asu.edu \
    --cc=mail@davie.li \
    --cc=me@bonfacemunyoki.com \
    --cc=pjotr2020@thebird.nl \
    --cc=rg@raghavgururajan.name \
    --cc=rprior@protonmail.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).