unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Catonano <catonano@gmail.com>
To: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>
Cc: "Guile User" <guile-user@gnu.org>, "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: [ANN] Guile Hall 0.3.0 released
Date: Mon, 18 May 2020 18:19:10 +0200	[thread overview]
Message-ID: <CAJ98PDykHaw_pJKL_PAGedzUqfEq=ZmgSts6Ucv6YzBv3WTB6w@mail.gmail.com> (raw)
In-Reply-To: <87y2pqcmox.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 347 bytes --]

Il giorno dom 17 mag 2020 alle ore 22:48 Alex Sassmannshausen <
alex.sassmannshausen@gmail.com> ha scritto:

Absolutely, thanks for offering!  Happy to give your draft a once over
> if you want!
>

So, here's the patch

is it leaning a bit too much on the use case illustration ?

Should it be a bit dryer to conform with the rest of the manual ?

[-- Attachment #2: guile-hall.patch --]
[-- Type: text/x-patch, Size: 2211 bytes --]

From b931125e04180305f7728c5f41e42e837974178b Mon Sep 17 00:00:00 2001
From: Adriano <catonano@gmail.com>
Date: Mon, 18 May 2020 17:44:15 +0200
Subject: [PATCH] added a reference t guile-hall in the manual

---
 doc/ref/scheme-using.texi | 50 +++++++++++++++++++++++++++++++++++++++
 1 file changed, 50 insertions(+)

diff --git a/doc/ref/scheme-using.texi b/doc/ref/scheme-using.texi
index ac265fcca..dfe298904 100644
--- a/doc/ref/scheme-using.texi
+++ b/doc/ref/scheme-using.texi
@@ -744,6 +744,56 @@ using a CPAN-like system.
 A complete list of guild scripts can be had by invoking @code{guild
 list}, or simply @code{guild}.
 
+@node guile-hall
+@subsection Bootstrapping projects and distributing them
+
+There's a tool that doesn't come bundled with Guile
+and yet it can be very useful in the common experience of using Guile.
+
+It's @uref{https://gitlab.com/a-sassmannshausen/guile-hall, guile-hall}
+
+When you start a new project guile-hall creates a folder
+containing a scaffold of your new project.
+
+In such scaffold the Autotools setup will be already instrumented,
+you don't need to take care of it yourself.
+
+Under the hood, guile-hall uses the Autoconf macros provided by Guile
+so the Autotools setup of your project will be able to test, for example,
+if a certain Guile library is available or if Guile itself is available and
+in which version.
+
+In this way you'll be able to call make to
+
+@itemize @bullet
+@item
+build your project
+@item
+run the unit tests
+@item
+create a distribution package (a .tar.gz file)
+@end itemize
+
+This covers 2 different needs.
+
+On one sie it assists you in working on your project
+by allowing you to conveniently build it and run the unit tests.
+
+On another side, when you're ready it will produce
+a manufact that lends itself to be easily distributed.
+
+GNU/Linux distributions will be able to easily
+distribute your project.
+
+But also people running a distribution that doesn't offer your project yet
+will be able to build and run it, provided they are acquainted with the
+usual process
+
+@example
+./configure
+make
+make install
+@end example
 
 @node Installing Site Packages
 @section Installing Site Packages
-- 
2.25.1


  reply	other threads:[~2020-05-18 16:19 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
2020-05-18  5:43               ` Arne Babenhauserheide
2020-05-17 20:48           ` Alex Sassmannshausen
2020-05-18 16:19             ` Catonano [this message]
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='CAJ98PDykHaw_pJKL_PAGedzUqfEq=ZmgSts6Ucv6YzBv3WTB6w@mail.gmail.com' \
    --to=catonano@gmail.com \
    --cc=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).