From: Christopher Allan Webber <cwebber@dustycloud.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Getting rid of build tools
Date: Tue, 29 Dec 2015 16:21:46 -0600 [thread overview]
Message-ID: <87mvssop4w.fsf@dustycloud.org> (raw)
In-Reply-To: <87mvst1d1v.fsf@gnu.org>
Ludovic Courtès writes:
> Pjotr Prins <pjotr.public12@thebird.nl> skribis:
>
>> For anyone interested, Eelco's description of Maak, a functional make,
>> is here:
>>
>> http://nixos.org/~eelco/pubs/iscsd-scm11-submitted.pdf
>
> It would be interesting to see what a Maak translated to Guile + Guix
> would look like.
>
> The ‘makeLibrary’, ‘compileC’, and other functions used as illustrations
> in the paper would be quite easy to write using our current APIs.
>
> Ludo’.
Reading this... it's interesting. It looks like Nix and Maak don't
share code, but do share ideas and contributors (and a founder)?
So, assuming we had that theoretical guix-make, would it be usable
without running Guix as a full package manager, or without running the
daemon necessarily? That might be more interesting, and in a way might
encourage more people to install Guix on their machines. If it can't be
done in a clean way, we shouldn't consider forcing that.
I worry a bit that not everyone will be willing to devote to using
/gnu/store/ and having the daemon on their distribution for building.
- Chris
next prev parent reply other threads:[~2015-12-29 22:40 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
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 [this message]
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=87mvssop4w.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=guix-devel@gnu.org \
--cc=ludo@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.