GNU bug report logs - #49158
Add ruby-for-crystal.

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#49158: closed (Add ruby-for-crystal.)
Date: Wed, 28 Sep 2022 18:37:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Wed, 28 Sep 2022 14:36:12 -0400
with message-id <875yh7uz1f.fsf <at> gmail.com>
and subject line Re: bug#49158: Add ruby-for-crystal.
has caused the debbugs.gnu.org bug report #49158,
regarding Add ruby-for-crystal.
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
49158: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=49158
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: "jgart" <jgart <at> dismail.de>
To: guix-patches <at> gnu.org
Cc: Raghav Gururajan <rg <at> raghavgururajan.name>, rprior <at> protonmail.com,
 mail <at> davie.li
Subject: Add ruby-for-crystal.
Date: Mon, 21 Jun 2021 16:19:40 +0000

[Message part 3 (text/plain, inline)]

Hi Guix,

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

This patch adds an old version of ruby that is required by the crystal language bootstrap process. This is related to 49142.

This was an effort of the volunteers at the last guix packaging meetup hosted by LibreMiami.

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 in guix:

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

There are 160 stages!

Some questions extracted from our 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

[0001-gnu-Add-ruby-for-crystal.patch (application/octet-stream, attachment)]

[Message part 5 (message/rfc822, inline)]

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: "jgart" <jgart <at> dismail.de>
Cc: Raghav Gururajan <rg <at> raghavgururajan.name>, 49158-done <at> debbugs.gnu.org,
 rprior <at> protonmail.com, mail <at> davie.li
Subject: Re: bug#49158: Add ruby-for-crystal.
Date: Wed, 28 Sep 2022 14:36:12 -0400

Hello,

"jgart" <jgart <at> dismail.de> writes:

> Hi Guix,
>
> We've (Ryan, David, Raghav, and others) started packaging crystal for guix: https://crystal-lang.org/
>
> This patch adds an old version of ruby that is required by the crystal
> language bootstrap process. This is related to 49142.

Since the crystal-lang patches haven't landed in more than a year,
I think it's safer to punt on this.

Closing.

Thanks!

Maxim

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.