From: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>
To: Arne Babenhauserheide <arne_bab@web.de>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-user@gnu.org
Subject: Re: [ANN] Guile Hall 0.3.0 released
Date: Sun, 17 May 2020 22:55:33 +0200 [thread overview]
Message-ID: <87wo5acmd6.fsf@gmail.com> (raw)
In-Reply-To: <87lflqtnv8.fsf@web.de>
Hi Arne,
Arne Babenhauserheide <arne_bab@web.de> writes:
> Catonano <catonano@gmail.com> writes:
>
>> Overall, I'd say this:
>>
>> […]
>>
>> There is level 0 of Guile packaging: that's NO packaging. You keep your
>> files scattered around and they will be autocompiled
>> In the future, there could be a level 2. That is: no m4 anymore !! As fas
>> as I undertsand the Autoconf based machinery relies on bash to execute
>> tests (is such library available ? Is Guile version >= 2.7 ?)
>
> Autoconf is intended to be bootstrappable with minimal dependencies.
> It needs some shell. At some point gash might be a suitable option.
Right. This is what autotools brings to the table right? A super
minimalist, dependable and portable installation process.
Having a fully Guile bootstrap using tools such as gash would be
amazing. It shouldn't lose us meaningful portability I suppose, because
these tools would work anywhere where Guile works, and we're talking
about distributing Guile libraries & applications in the first place!
> m4 is just a very simple templating language. Should not be too hard
> to implement it in Guile.
Again, this has come up in the past. I love the idea of having a Guile
way to do the work that m4, autoreconf and automake do — I think any
piecemeal or module work towards this would super valuable.
I hope for now, in the absence of those things existing, having Hall
provide a kludgy bridge between autotools and Guile might be the best of
both worlds…
Cheers,
Alex
next prev parent reply other threads:[~2020-05-17 20:55 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 15:41 [ANN] Guile Hall 0.3.0 released Alex Sassmannshausen
2020-05-16 16:14 ` Jack Hill
2020-05-16 16:22 ` Catonano
2020-05-16 20:57 ` Alex Sassmannshausen
2020-05-17 5:13 ` Catonano
2020-05-17 15:35 ` Alex Sassmannshausen
2020-05-17 17:37 ` Catonano
2020-05-17 18:31 ` Arne Babenhauserheide
2020-05-17 20:55 ` Alex Sassmannshausen [this message]
2020-05-18 5:43 ` Arne Babenhauserheide
2020-05-17 20:48 ` Alex Sassmannshausen
2020-05-18 16:19 ` Catonano
2020-05-20 11:45 ` Catonano
2020-05-20 11:46 ` Alex Sassmannshausen
2020-05-20 15:58 ` Catonano
2020-05-21 10:00 ` Catonano
2020-05-21 10:03 ` Alex Sassmannshausen
2020-05-22 5:16 ` Catonano
2020-05-24 21:22 ` Alex Sassmannshausen
2020-05-25 6:31 ` Catonano
2020-05-25 7:13 ` Alex Sassmannshausen
2020-05-25 7:51 ` Catonano
2020-05-26 14:37 ` Catonano
2020-05-27 20:52 ` Ludovic Courtès
2020-05-28 5:01 ` Catonano
2020-05-28 12:32 ` Ludovic Courtès
2020-05-28 12:35 ` Catonano
2020-05-28 15:54 ` Ludovic Courtès
2020-05-28 17:26 ` Catonano
2020-05-29 8:27 ` Ludovic Courtès
2020-05-29 9:09 ` Catonano
2020-05-29 10:52 ` Alex Sassmannshausen
2020-05-17 16:36 ` Christopher Lemmer Webber
2020-05-17 20:40 ` Alex Sassmannshausen
2020-05-17 20:21 ` Jérémy Korwin-Zmijowski
2020-05-18 15:43 ` Nala Ginrut
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wo5acmd6.fsf@gmail.com \
--to=alex.sassmannshausen@gmail.com \
--cc=arne_bab@web.de \
--cc=guile-user@gnu.org \
--cc=ludo@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).