From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: Guix as a Guile package manager Date: Sat, 09 Jan 2016 20:47:08 +0100 Message-ID: <87h9im4jsz.fsf@elephly.net> References: <5690E261.8000704@gnu.org> <569113EF.5060605@gnu.org> <138b89e2a7ca9e091727a331a416bd6a@hypermove.net> <56912749.5030501@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: In-reply-to: <56912749.5030501@gnu.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org To: Fabio Pesari Cc: guix-devel@gnu.org, guile-devel@gnu.org, Amirouche Boubekki List-Id: guix-devel.gnu.org Fabio Pesari 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