From: 宋文武 <iyzsong@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Gammel Holte" <gammel.holte@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Optional runtime dependencies in Guix
Date: Mon, 12 Jan 2015 21:11:36 +0800 [thread overview]
Message-ID: <87vbkcxhx3.fsf@gmail.com> (raw)
In-Reply-To: <87twzwuyn9.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> Gammel Holte <gammel.holte@gmail.com> skribis:
>
>> For example, consider samtools, a package I use daily and that was recently
>> committed to Guix:
>>
>> http://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/bioinformatics.scm#n139
>>
>> It forces me to install python. In contrast, consider Arch AUR's package:
>>
>> https://aur.archlinux.org/packages/samtools/
>
> From looking at the page above, it seems that it would be feasible to
> simply move varfilter.py 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?
Move it to a different output should work, but the 'python' output
doesn't make much sense to me compare to 'doc', 'bin' and 'debug'.
Note that 'python' is not a build dependency of 'samtools', so we
can only patch '#!/usr/bin/env' but not 'python' for varfilter.py.
Then we should give recommends or suggests, user need it could
install python manually.
>
>> An extreme example of this is weechat:
>>
>> http://lists.gnu.org/archive/html/guix-devel/2014-09/msg00229.html
>>
>> Compare with:
>>
>> https://www.archlinux.org/packages/extra/i686/weechat/
>>
>> 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?
This is total different, those plugins must live in $out/lib/plugins
to work (can't move to seperated outputs).
Keep in mind that interpreters are both build and runtime dependencies
of weechat, the nature way is making them optional when building:
(define-public (%weechat #:key (python? #t)
(guile? #t)
...
(package
(inputs
`(("python" ,(if python? python #nil))
("guile" ,(if guile? guile #nil))
...
(define-public weechat (%weechat)) ; our default version
Then user can install the customized version with:
$ guix package -e '((@ (gnu packages weechat) %weechat) #:python? #f)'
>
> 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.
>
> Thanks,
> Ludo’.
next prev parent reply other threads:[~2015-01-12 13:11 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
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 ` 宋文武 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vbkcxhx3.fsf@gmail.com \
--to=iyzsong@gmail.com \
--cc=gammel.holte@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.