unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Fabio Pesari <fabiop@gnu.org>
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: guix-devel <guix-devel@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: Guix as a Guile package manager
Date: Sat, 9 Jan 2016 17:00:46 +0100	[thread overview]
Message-ID: <56912EAE.5050308@gnu.org> (raw)
In-Reply-To: <CAJ=RwfbaJfy_sOii582S3P12Mdj9AkMd1E30uG3_Kww88McZ9A@mail.gmail.com>

On 01/09/2016 04:30 PM, Thompson, David wrote:
>
> I don't think Guix is a good fit here, because there's simply no way
> around the fact that Guix packages *must* contain the full dependency
> graph for build-time and runtime dependencies.  There's no way that
> you could use, say, the Guile or GCC from your host system because
> doing so invalidates the entire purpose and design of Guix.  Thus, a
> Debian user that tried to use a Guile-specific package manager based
> on Guix would be surprised when it starts compiling its own glibc,
> GCC, Guile, etc.  So, I don't see anything worth extracting from Guix
> to use to build a Guile-specific package manager.

Hello David,

and thank you for your answer!

As a simple user, I didn't know enough about the finer points of Guix in
this context so I really appreciate your answer. I thought some of Guix'
package management functionalities could be worked into a less specific
program but if it can't be done, it can't be done!

> I encourage you to hack on Guildhall to make it more usable for your
> needs.

I've seen people work on dozens of package managers over the years and
honestly, I don't feel like working on one unless it's officially part
of the language or it already has mainstream adoption.

It's a Catch 22, I know, but those projects all amount to re-inventing
the wheel and trying to solve the same problems over and over again
until they get abandoned because nobody uses them (like it happened with
Guildhall, last updated in June).

I know Guile was designed as an extension language so it is excused from
not having a package manager, but with the latest developments and Guix
in particular I thought the language was heading in a more
general-purpose direction and that's why I posted this proposal.



  reply	other threads:[~2016-01-09 16:00 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
2016-01-09 15:30 ` Thompson, David
2016-01-09 16:00   ` Fabio Pesari [this message]
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=56912EAE.5050308@gnu.org \
    --to=fabiop@gnu.org \
    --cc=dthompson2@worcester.edu \
    --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).