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: Tue, 3 Jul 2018 09:03:38 +0200 [thread overview]
Message-ID: <CAKdwf2AET88kYHr3kxOBSof39-vJVVizkTbMMbp8eCrHA-0F6A@mail.gmail.com> (raw)
In-Reply-To: <87zhz9fze5.fsf@gnu.org>
On Mon, 2 Jul 2018, 17:09 Ludovic Courtès, <ludo@gnu.org> wrote:
> Heya,
>
> Alex Sassmannshausen <alex.sassmannshausen@gmail.com> skribis:
>
> >> 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?
>
> I’m thinking of a “hall build” command that would build Scheme files and
> produce a wrapper script, and optionally “hall install” as well.
> It’s interesting only if it can be done without reimplementing too much
> of the Autoconf/Automake or Guix logic, I suppose.
>
Agreed. I do think having some easy way of "running" your project would be
cool.
Thanks for your thoughts!
Alex
next prev parent reply other threads:[~2018-07-03 7:03 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
2018-07-02 15:09 ` Ludovic Courtès
2018-07-03 7:03 ` alex sassmannshausen [this message]
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=CAKdwf2AET88kYHr3kxOBSof39-vJVVizkTbMMbp8eCrHA-0F6A@mail.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).