all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org
Subject: Re: Getting rid of build tools
Date: Tue, 29 Dec 2015 02:47:23 +0100	[thread overview]
Message-ID: <20151229014722.GA6686@thebird.nl> (raw)
In-Reply-To: <20151228190536.GA5914@thebird.nl>

On Mon, Dec 28, 2015 at 08:05:36PM +0100, Pjotr Prins wrote:
> On Mon, Dec 28, 2015 at 09:06:40AM -0600, Christopher Allan Webber wrote:
> I agree. It is actually in line with Eelco Dolstra's thinking more
> than 10 years ago (he created 'Maak'), though he did not use Guile.
> 
> I am not saying we don't need build tools altogether - I'll still use
> make and rake, for example. But we certainly don't need all the
> baggage that comes with the current set of 'complex' Makefile
> generation tools that are automake and cmake. I guess it should be
> somewhere in between :). Yes a configurable Guile solution would be
> excellent.

For anyone interested, Eelco's description of Maak, a functional make,
is here:

  http://nixos.org/~eelco/pubs/iscsd-scm11-submitted.pdf

-- 

  reply	other threads:[~2015-12-29  1:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-27  8:23 Getting rid of build tools Pjotr Prins
2015-12-28 15:06 ` Christopher Allan Webber
2015-12-28 19:05   ` Pjotr Prins
2015-12-29  1:47     ` Pjotr Prins [this message]
2015-12-29  2:42       ` Pjotr Prins
2015-12-29  7:22         ` Ricardo Wurmus
2015-12-29 15:26           ` Pjotr Prins
2015-12-29 15:37       ` Ludovic Courtès
2015-12-29 15:40         ` Pjotr Prins
2015-12-29 22:21         ` Christopher Allan Webber
2015-12-29 23:41           ` Ludovic Courtès
2016-01-01  7:16         ` Pjotr Prins
2015-12-29 15:33     ` Ludovic Courtès
2015-12-29 15:39       ` Pjotr Prins
2016-01-06  5:22   ` Pjotr Prins

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=20151229014722.GA6686@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --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.