From: ludo@gnu.org (Ludovic Courtès)
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Guix-based build tool
Date: Wed, 18 Apr 2018 23:06:53 +0200 [thread overview]
Message-ID: <87k1t4teaa.fsf@gnu.org> (raw)
In-Reply-To: <87po2x2mwo.fsf@gmail.com> (Chris Marusich's message of "Tue, 17 Apr 2018 20:50:31 -0700")
Hi Chris & Chris, :-)
Chris Marusich <cmmarusich@gmail.com> skribis:
> Christopher Lemmer Webber <cwebber@dustycloud.org> writes:
>
>> David Thompson has made many comments before on the mistake of mixing
>> build systems and package managers... I'm a bit worried that we might be
>> encouraging going down that same path?
>
> The Guix daemon implements the functional software deployment model.
> That model can, in theory, be used to create various things. One of
> those things is a package manager. Another of those things is a
> continuous integration server farm (e.g., Hydra, Cuirass). Another of
> those things is a make-like build system (not yet created).
Exactly, that was the spirit of my suggestion.
Now I’d be interested in reading David’s arguments!
Ludo’.
next prev parent reply other threads:[~2018-04-18 21:07 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
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 [this message]
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=87k1t4teaa.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=cmmarusich@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 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).