From: julien lepiller <julien@lepiller.eu>
To: guix-devel@gnu.org
Subject: Re: Guix-based build tool
Date: Mon, 09 Apr 2018 17:53:03 +0200 [thread overview]
Message-ID: <7d2f78af89b8dc380a881176a2011550@lepiller.eu> (raw)
In-Reply-To: <87vad0ieie.fsf_-_@gnu.org>
Le 2018-04-09 17:30, ludo@gnu.org a écrit :
> Hello!
>
> Pjotr Prins <pjotr.public12@thebird.nl> skribis:
>
>> Indeed, I love working with Guix and developing with Guix. Guix takes
>> care of my deployment and configuration requirements.
>>
>> I have written some time in the past that with Guix you don't need
>> autotools. The main thing autotools solve is configuring the build for
>> an environment. At the same time, with Guix you get a predictable
>> environment, so a make file (or similar) suffices. It is what I do in
>> all my development projects - I don't use autotools to develop and
>> deploy them. It greatly simplifies my existence :). Indeed, I have
>> never liked autotools (essentially a nasty hack) and only used them
>> before Nix/Guix. So, my approach is the same as yours :)
>
> +1!
>
> If we could provide tooling with an abstraction level close to that of
> a
> makefile, that’d help a lot.
I don't really agree mixing a package manager and a build tool is a
good idea. Sure, it helps a lot because they both solve the same kind
of problem and I certainly see what advantage it would have, but so do
maven devs. They mixed a package manager and a build system together.
It became the official way to build many packages, including its own
dependencies. As a result, it became a total mess to build maven from
scratch. So if someone wants to build a package whose only build
system is guix but can't use guix for some reason (maybe it wasn't
ported to their platform?) will just cry and hate us.
>
> Actually, just like we have ‘emacs-build-system’, we could very much
> add
> ‘guile-build-system’ for simple Guile packages that don’t need/use
> Autoconf & co.
That's more reasonable though :)
>
> ‘guile-build-system’ would automatically run ‘guild compile’,
> ‘makeinfo’, etc. pretty much like we do here:
>
>
> https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/guile.scm#n870
>
> Once we have that, developers of Guile packages can simply drop a
> ‘.guix’ file in their project and use it with ‘guix environment’, ‘guix
> build’, and ‘guix package’.
>
> That’s coarser-grain than a makefile, of course, but would be a good
> first step to providing tooling for people working on Guile code.
>
> Any takers for ‘guile-build-system’?
>
>
> A next step could be to add a tool that understands a syntax like that
> of the guildhall, which gets us closer to the makefile/Makefile.am
> level
> of abstraction:
>
> https://github.com/ijp/guildhall/blob/master/docs/packaging.texi#L121
>
> Ludo’.
next prev parent reply other threads:[~2018-04-09 15:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 8:58 a blog post Catonano
2018-04-06 22:07 ` Autotools formely: " Pjotr Prins
2018-04-09 15:30 ` Guix-based build tool Ludovic Courtès
2018-04-09 15:53 ` julien lepiller [this message]
2018-04-11 8:02 ` Catonano
2018-04-16 16:59 ` Christopher Lemmer Webber
2018-04-18 3:50 ` Chris Marusich
2018-04-18 21:06 ` Ludovic Courtès
2018-04-18 21:09 ` Ludovic Courtès
2018-04-19 16:49 ` Catonano
2018-04-20 6:52 ` Catonano
2018-04-20 6:58 ` Catonano
2018-04-23 15:53 ` Ludovic Courtès
2018-04-20 20:13 ` Ricardo Wurmus
2018-04-07 3:35 ` a blog post Erik Edrosa
2018-04-07 9:53 ` Hartmut Goebel
2018-04-07 10:46 ` Tobias Geerinckx-Rice
2018-04-07 10:59 ` Catonano
2018-04-09 0:18 ` Chris Marusich
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7d2f78af89b8dc380a881176a2011550@lepiller.eu \
--to=julien@lepiller.eu \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).