From: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-user@gnu.org
Subject: Re: [ANN] Guile Hall Release (v0.1.1)
Date: Mon, 02 Jul 2018 11:47:14 +0200 [thread overview]
Message-ID: <87zhzat1el.fsf@gmail.com> (raw)
In-Reply-To: <877emepudc.fsf@gnu.org>
Hi Ludo,
Ludovic Courtès writes:
> Hello Alex,
>
> Alex Sassmannshausen <alex.sassmannshausen@gmail.com> skribis:
>
>> Otherwise you can get the code from
>> https://gitlab.com/a-sassmannshausen/guile-hall/, and build (hopefully)
>> using the traditional
>> $ autoreconf -vif && ./configure && make
>> dance.
>>
>> What is Guile Hall?
>>
>> From the README:
>>
>> Hall is a command-line application and a set of Guile libraries that
>> allow you to quickly create and publish Guile projects. It allows you
>> to transparently support the GNU build system, manage a project
>> hierarchy & provides tight coupling to Guix.
>
> This looks really great! There’s this longstanding issue with
> distributing Guile code, and this seems to be a good approach.
>
> In particular, that it’s not a Guix-only solution, while at the same
> time offering Guix support is really a wise choice.
Thanks for your kind and thoughtful notes :-)
> I think we should advertise it widely, it’ll be immensely helpful to
> newcomers. When the manual is more complete ;-), we could refer to it
> from guile.texi, too.
That would be wonderful — I'm particularly interested in hearing from
relative newcomers as to the user journey and/or ease of use!
I anticipate I'll be adding a manual for the next release or so, but I
want to see how the project performs in my own world, and in public for
a while first. It may need some re-architecturing!
> I wonder if it would be useful to have a “standalone” mode, where Hall
> would rely neither on Autoconf/Automake nor on Guix to do basic things
> like building code. It might help newcomers. You wouldn’t want to
> reimplement everything though, so I don’t know if this is a viable
> approach. Thoughts?
Interesting idea. When you say building code, do you mean literally
compiling a project within the project folder & perhaps generating a
wrapper script that might update GUILE_LOAD_{COMPILED_}PATH à la
pre-inst-env, or do you mean some form of installer?
My thinking guiding the project so far is that I think Guix is the
de-facto Guile package manager, and as such I want to encourage an easy
user-journey for people towards using/contributing to it. But if we can
offer a fully stand-alone "run your self-contained Guile project with no
dependencies" workflow, which offers a user journey to autotools/guix
distribution without the user having to do any additional work, then
that might certainly be interesting!
> Thank you!
>
> Ludo’.
Thank you for your comments!
Alex
next prev parent reply other threads:[~2018-07-02 9:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-01 12:07 [ANN] Guile Hall Release (v0.1.1) Alex Sassmannshausen
2018-07-01 20:35 ` Ludovic Courtès
2018-07-02 9:47 ` Alex Sassmannshausen [this message]
2018-07-02 15:09 ` Ludovic Courtès
2018-07-03 7:03 ` alex sassmannshausen
2018-07-03 7:27 ` Aw: " Arne Babenhauserheide
2018-07-03 8:07 ` alex sassmannshausen
2018-07-03 19:59 ` Arne Babenhauserheide
2019-02-19 7:26 ` Catonano
2019-02-19 19:05 ` Alex Sassmannshausen
2019-02-19 19:44 ` Jérémy Korwin-Zmijowski
2019-02-24 16:10 ` Alex Sassmannshausen
2018-07-01 22:51 ` Amirouche Boubekki
2018-07-02 9:39 ` Alex Sassmannshausen
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=87zhzat1el.fsf@gmail.com \
--to=alex.sassmannshausen@gmail.com \
--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).