From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Call for project proposals: Guix and Outreachy
Date: Sat, 27 Jan 2018 03:01:56 +0100 [thread overview]
Message-ID: <20180127020156.pw4pjxijbxlkyaew@floriannotebook> (raw)
In-Reply-To: <874ln896pq.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]
Hello,
On Fri, Jan 26, 2018 at 12:53:37PM +0100, Alex Sassmannshausen wrote:
> A second step might be a simplified Guile build system, which does not
> rely on autotools infrastructure. I believe this was discussed in the
> past: it would be a "beginners build system" for *Guile only* packages
> for quick and easy sharing in the Guix community.
>
By beginners build system, do you mean a Guix build system that just
copies the modules directory and compiles?
Forgive my ignorance as someone who has no deep understanding of
Guile/Guix, but I think it would be better if even simple Guile only
packages used a build system like Meson or Autotools. Even Guile only
packages should not need Guix or manual copying. The syntax of
Autotools is too complicated IMHO, but using a general purpose build
system like Meson for simple C projects is no more work than listing
the source files and data files like pkg-config and this should apply
to Guile projects as well.
That said, a beginners Guix build system for pure Guile projects is
done much more easily than making simple general purpose build systems
support Guile. I’d like to take a look at Meson support for Guile and
Guile implementations of Ninja and Meson, but I probably can’t/won’t
commit the time… Well maybe…
Regards,
Florian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-01-27 2:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-21 21:59 Call for project proposals: Guix and Outreachy Ricardo Wurmus
2018-01-26 11:53 ` Alex Sassmannshausen
2018-01-27 2:01 ` pelzflorian (Florian Pelz) [this message]
2018-01-27 11:45 ` Alex Sassmannshausen
2018-01-28 16:42 ` Ricardo Wurmus
2018-01-29 11:11 ` Alex Sassmannshausen
2018-02-06 22:05 ` Ricardo Wurmus
2018-02-07 7:51 ` Gábor Boskovits
2018-02-07 9:58 ` Ricardo Wurmus
2018-02-07 10:45 ` Gábor Boskovits
2018-02-08 13:47 ` Ludovic Courtès
2018-02-07 10:57 ` Andreas Enge
2018-02-08 13:48 ` Ludovic Courtès
2018-02-08 16:23 ` Ricardo Wurmus
2018-02-08 19:26 ` Gábor Boskovits
2018-02-08 19:58 ` Ricardo Wurmus
2018-02-10 7:08 ` Gábor Boskovits
2018-02-10 3:06 ` Chris Marusich
2018-02-10 6:52 ` Gábor Boskovits
2018-02-10 10:12 ` Ricardo Wurmus
2018-02-07 10:52 ` Andreas Enge
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180127020156.pw4pjxijbxlkyaew@floriannotebook \
--to=pelzflorian@pelzflorian.de \
--cc=alex.sassmannshausen@gmail.com \
--cc=guix-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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.