[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Optional runtime dependencies in Guix

From: Ludovic Courtès
Subject: Re: Optional runtime dependencies in Guix
Date: Mon, 12 Jan 2015 10:38:34 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux)

Gammel Holte <address@hidden> skribis:

> For example, consider samtools, a package I use daily and that was recently
> committed to Guix:
> It forces me to install python. In contrast, consider Arch AUR's package:

>From looking at the page above, it seems that it would be feasible to
simply move to a different output.  That way, users would
be able to install the default output (which doesn’t depend on Python),
or the “python” output.  Ricardo, WDYT?

> An extreme example of this is weechat:
> Compare with:
> Guix version forces the user to install all interpreters for running
> user-defined scripts to extend Weechat. These are quite many: lua, perl,
> python, ruby, tcl (and guile).

Yes, I hadn’t noticed this and I agree this is problematic.

Kevin, any idea on how to split things?

As I wrote before, there’s no one-size-fits-all recipe to address the
problem, just a couple of usable patterns (basically separate outputs or
separate packages.)  So we need to address this mostly on a case-by-case
basis, and also probably clarify this in the packaging guidelines.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]