From: Nala Ginrut <nalaginrut@gmail.com>
To: alex.sassmannshausen@gmail.com
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Guile Hall 0.2.1 Released
Date: Fri, 17 Jan 2020 23:54:37 +0800 [thread overview]
Message-ID: <CAPjoZodycyyC0qWKQnohVzu4UWJ_R_nB_DZbCU2tBHXE7LKq3Q@mail.gmail.com> (raw)
In-Reply-To: <87y2u619o8.fsf@gmail.com>
nice work!
On Fri, Jan 17, 2020 at 9:44 PM Alex Sassmannshausen <
alex.sassmannshausen@gmail.com> wrote:
> Hello,
>
> I've just released Guile Hall 0.2.1. It is primarily a maintenance
> release to support Guile 3.0. This means it should work with Guile 3
> and it should also make any project managed through hall (by using the
> `hall dist` command) work with Guile 3.0.
>
> Beyond this the new release includes a greatly expanded manual, and some
> smaller tweaks and bug fixes.
>
> You can get it with Guix after pulling the latest version with
> $ guix package -i guile-hall
>
> Otherwise you can get the code from
> https://gitlab.com/a-sassmannshausen/guile-hall/
>
> After installing autoconf, automake, pkg-config and texinfo, you can
> perform the usual
> autoreconf -vif && ./configure && make && make install
>
> 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.
>
> It's fundamental aim is to provide a black box that just works (tm)
> for you so you distribute, manage & create guile projects.
>
> This project is part of my overall goal of creating user-friendly basic
> tooling & libraries for Guile to encourage newbies to start building
> with Guile.
>
> Best wishes,
>
> Alex
>
>
prev parent reply other threads:[~2020-01-17 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 13:42 Guile Hall 0.2.1 Released Alex Sassmannshausen
2020-01-17 15:54 ` Nala Ginrut [this message]
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=CAPjoZodycyyC0qWKQnohVzu4UWJ_R_nB_DZbCU2tBHXE7LKq3Q@mail.gmail.com \
--to=nalaginrut@gmail.com \
--cc=alex.sassmannshausen@gmail.com \
--cc=guile-user@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).