From: Ricardo Wurmus <rekado@elephly.net>
To: Fabio Pesari <fabiop@gnu.org>
Cc: guix-devel@gnu.org, guile-devel@gnu.org,
Amirouche Boubekki <amirouche@hypermove.net>
Subject: Re: Guix as a Guile package manager
Date: Sat, 09 Jan 2016 20:47:08 +0100 [thread overview]
Message-ID: <87h9im4jsz.fsf@elephly.net> (raw)
In-Reply-To: <56912749.5030501@gnu.org>
Fabio Pesari <fabiop@gnu.org> writes:
> The way I see it:
>
> * Guile ships with guile-guix (a library that implements much of Guix'
> package management capabilities, but not the Guix program) and a
> (very small) Guile package manager which depends on guile-guix
The package management capabilities provided by Guix only make sense in
the world of functional package management where the complete graph of
dependencies is captured, all the way down to bootstrap libraries.
If you take away functional package management (e.g. because it’s
inconvenient in a simple language-specific package manager), you won’t
need the guix-daemon anymore, nor do you need to talk to it anymore, nor
do you need to actually be able to represent the complete graph of
inputs ... and you end up throwing away pretty much everything that Guix
provides.
> * Guix is distributed separately as a (very small) program which
> depends on guile-guix
The commands provided by Guix are tiny Guile scripts that use the bulk
of Guix as a library. In a sense “guile-guix” already exists: it’s
called Guix :) But it’s the wrong library for a language-specific
package manager.
~~ Ricardo
next prev parent reply other threads:[~2016-01-09 19:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 10:35 Guix as a Guile package manager Fabio Pesari
2016-01-09 13:05 ` Amirouche Boubekki
2016-01-09 14:06 ` Fabio Pesari
2016-01-09 14:35 ` Amirouche Boubekki
2016-01-09 15:29 ` Fabio Pesari
2016-01-09 19:47 ` Ricardo Wurmus [this message]
2016-01-09 15:30 ` Thompson, David
2016-01-09 16:00 ` Fabio Pesari
2016-01-09 18:52 ` Ludovic Courtès
2016-01-09 20:42 ` Leo Famulari
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h9im4jsz.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=amirouche@hypermove.net \
--cc=fabiop@gnu.org \
--cc=guile-devel@gnu.org \
--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.
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).