From: Amirouche Boubekki <amirouche.boubekki@gmail.com>
To: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>
Cc: Arne Babenhauserheide <arne_bab@web.de>,
guile-devel <guile-devel@gnu.org>
Subject: Re: FOSDEM 2019
Date: Wed, 6 Feb 2019 16:22:08 +0100 [thread overview]
Message-ID: <CAL7_Mo8Ya5N+tUJpb56w+FSpbg=k_=y043is5CUiELxOcCu6Dw@mail.gmail.com> (raw)
In-Reply-To: <87o97pc9m9.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1376 bytes --]
Le mer. 6 févr. 2019 à 14:47, Alex Sassmannshausen <
alex.sassmannshausen@gmail.com> a écrit :
> > - Janneke mentioned the new guile build system in guix for simpler
> > guile packages and I think that's pretty great. Likewise there was
> > some mention of some sort of you-don't-have-to-use-autotools build
> > system and I don't remember what it's name was. (BTW, I continue to
> > believe that "Guix is and should be Guile's package mangager".)
>
> I was unaware that we had a guile build system in Guix.
What is it?
> In the past I was the one who argued strongly for the build system and
> for the no-autotools approach — I believe in the context of outreachy.
> Unfortunately I was unable to make that part a reality.
>
> Even so, I have been developing a solution that is part of this
> discussion in the form of Guile Hall, which is a project manager for
> Guile with strong integration with Guix & Autotools.
>
guile hall can be found here https://gitlab.com/a-sassmannshausen/guile-hall
> As you can see, I have a horse in this race. I would be very interested
> in collaborating with others who feel strongly about this part of the
> Guile/Guix user journey — either on improvements to Hall, Guix or on
> other tooling.
>
Talking about tools and build systems, what do you think of https://waf.io/?
[-- Attachment #2: Type: text/html, Size: 2284 bytes --]
next prev parent reply other threads:[~2019-02-06 15:22 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-03 21:34 FOSDEM 2019 Mikael Djurfeldt
2019-02-03 23:13 ` Arne Babenhauserheide
2019-02-04 5:21 ` Nala Ginrut
2019-02-05 21:25 ` Christopher Lemmer Webber
2019-02-06 13:46 ` Alex Sassmannshausen
2019-02-06 15:22 ` Amirouche Boubekki [this message]
2019-02-06 15:33 ` Amirouche Boubekki
2019-02-06 15:42 ` Alex Sassmannshausen
2019-02-06 21:03 ` Ricardo Wurmus
2019-02-06 22:09 ` Alex Sassmannshausen
2019-02-26 8:57 ` swedebugia
2019-02-06 20:40 ` Arne Babenhauserheide
2019-02-05 21:26 ` Christopher Lemmer Webber
2019-02-04 13:06 ` Amirouche Boubekki
2019-02-04 14:44 ` Ludovic Courtès
2019-02-04 18:01 ` Jan Nieuwenhuizen
2019-02-05 11:09 ` Amirouche Boubekki
2019-02-05 16:58 ` Ludovic Courtès
2019-02-06 0:31 ` Nala Ginrut
2019-02-06 12:59 ` Ludovic Courtès
2019-02-06 19:09 ` Amirouche Boubekki
2019-02-06 0:37 ` Matt Wette
2019-02-06 0:56 ` Nala Ginrut
2019-02-06 1:40 ` Amirouche Boubekki
2019-02-05 2:30 ` Matt Wette
-- strict thread matches above, loose matches on Subject: below --
2018-08-21 13:33 Manolis Ragkousis
2018-08-21 17:57 ` Ricardo Wurmus
2018-08-22 16:27 ` Andy Wingo
2018-08-22 2:33 ` Mike Gran
2018-08-23 0:08 ` Mike Gran
2018-08-24 12:23 ` Christopher Lemmer Webber
2018-08-29 21:08 ` Ludovic Courtès
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='CAL7_Mo8Ya5N+tUJpb56w+FSpbg=k_=y043is5CUiELxOcCu6Dw@mail.gmail.com' \
--to=amirouche.boubekki@gmail.com \
--cc=alex.sassmannshausen@gmail.com \
--cc=arne_bab@web.de \
--cc=guile-devel@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).