From: ludo@gnu.org (Ludovic Courtès)
To: Gammel Holte <gammel.holte@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Optional runtime dependencies in Guix
Date: Sun, 23 Nov 2014 21:47:03 +0100 [thread overview]
Message-ID: <87zjbh3arc.fsf@gnu.org> (raw)
In-Reply-To: <CAGFCsG_uRr0R2bQ40g4d_K2NkUCENQJmpwws8fh3yFuaPrYMdw@mail.gmail.com> (Gammel Holte's message of "Sun, 23 Nov 2014 03:43:13 +0000")
Hello,
Gammel Holte <gammel.holte@gmail.com> skribis:
> Nix doesn't have a good decoupling between packages and their optional
> runtime dependencies. You can disable them, but this would lead to a
> different package hash, and thus a different build (negating the use of
> prebuilt binaries).
>
> Therefore, the culture seems to have all default package builds with all
> optional runtime dependencies on. This leads to situations such as
> installing mutt, and getting python as a dependency (via mutt -> gpgme ->
> glib -> python), which is quite ugly.
That’s indeed undesirable.
As I just wrote to Taylan Ulrich, this is currently handled on a
case-by-case basis using multiple outputs (which I think Nixpkgs doesn’t
use a lot yet.)
For instance, GLib has a separate “bin” output for this very reason (see
<http://bugs.gnu.org/17853>.) Git, as I wrote, has separate outputs for
git-svn and Tcl stuff. Same for WordNet. There are also separate
outputs for debugging symbols.
So I wouldn’t claim this is a solved problem, because it really gets
fixed when we discover a problematic case, and we certainly overlook
some of them. Yet, that’s something I pay attention to, and I think we
must clearly look to address more of such issues.
WDYT?
Thanks,
Ludo’.
next prev parent reply other threads:[~2014-11-23 20:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-23 3:43 Optional runtime dependencies in Guix Gammel Holte
2014-11-23 20:47 ` Ludovic Courtès [this message]
2015-01-11 15:38 ` Gammel Holte
2015-01-12 9:38 ` Ludovic Courtès
2015-01-12 11:23 ` Ricardo Wurmus
2015-01-12 16:03 ` Ludovic Courtès
2015-01-12 13:11 ` 宋文武
2015-01-12 16:26 ` Ludovic Courtès
2015-01-12 18:47 ` Andreas Enge
2015-01-12 19:18 ` Gammel Holte
2015-01-13 17:28 ` Ludovic Courtès
2015-01-13 17:24 ` Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zjbh3arc.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=gammel.holte@gmail.com \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).