From: Andreas Reuleaux <rx@a-rx.info>
To: "help-guix" <help-guix@gnu.org>
Subject: Re: Packaging Idris2
Date: Sun, 21 Aug 2022 11:21:28 +0100 [thread overview]
Message-ID: <87zgfxrj6f.fsf@softland> (raw)
In-Reply-To: <CMBJ4UPWNQQA.3DM0P0V8YAY01@guix-aspire> (paren@disroot.org's message of "Sun, 21 Aug 2022 08:31:12 +0100")
"(" <paren@disroot.org> writes:
> Hi Andreas,
>
> On Sat Aug 20, 2022 at 11:01 PM BST, Andreas Reuleaux wrote:
>> You bootstrap it from scheme (chez or racket), as comes within the Idris2 tarball
>> (and built with Idris 2 itself: Idris2 -> Chez Scheme / Racket).
>
> Since this Scheme is pregenerated, it cannot really count as source code. So
> we need to find a version of Idris2 that can still be built with Idris1, then
> try to build a later version with that Idris2, and keep going until we get to
> the latest version, like our rustc bootstrap process.
>
> -- (
OK, thanks for getting back to me, and I am learning...
Nevertheless: this sounds terribly complicated to me.
Why would I use a package manager then (the guix package manager i.e.) in the
first place, if I can install idris2 in just simple three steps:
step 1
download https://www.idris-lang.org/idris2-src/idris2-0.5.1.tgz
and unpack it.
step 2
adjust PREFIX in config.mk therein ($(HOME)/opt/idris2 in my case)
and set PATH, and LD_LIBRARY_PATH accordingly:
export PATH=$PATH:$HOME/opt/idris2/bin
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$HOME/opt/idris2/lib
step 3
(assuming racket is installed - as in my case):
make bootstrap-racket
make install
And In particular: there is no Idris1 involved.
(And by the way: the pregenerated scheme in there is not a binary,
it is readable scheme code after all - well not terribly readable,
but nevertheless).
What is won with the extra step of having an older Idris2 installed
first, that still compiles with Idris 1 - And then do what with that:
compile a newer Idris2 from that (that may still not be sufficiant
to compile the latest Idris2), ... Reproducibility ? - Certainly
not simplicity!
But apparently: you are more experienced in these packaging matters
then me.
So thanks - in any case.
And by the way: my bench marks were on a 8 core
Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz
running Debian testing)
-A
next prev parent reply other threads:[~2022-08-21 10:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 15:42 Packaging Idris2 Pierre-Henry Fröhring
2022-08-19 19:54 ` (
2022-08-20 0:11 ` Pierre-Henry Fröhring
2022-08-20 18:42 ` Csepp
2022-08-20 22:01 ` Andreas Reuleaux
2022-08-21 7:31 ` (
2022-08-21 8:42 ` Csepp
2022-08-21 10:21 ` Andreas Reuleaux [this message]
2022-08-21 10:39 ` (
2022-08-21 10:41 ` (
2022-08-21 12:31 ` zimoun
2022-08-21 23:40 ` Philip McGrath
2022-08-23 7:56 ` contact
2022-08-23 11:39 ` Csepp
2022-08-23 13:02 ` contact
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=87zgfxrj6f.fsf@softland \
--to=rx@a-rx.info \
--cc=help-guix@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.
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).