From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] Add (minimal) BioPerl.
Date: Sat, 6 Jun 2015 19:52:50 +0200 [thread overview]
Message-ID: <87d218wwp9.fsf@mdc-berlin.de> (raw)
In-Reply-To: <87sia44tjs.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:
>
>> From e8cffdb9e7a2447657b3f700b2f0beb00ad0f98e Mon Sep 17 00:00:00 2001
>> From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
>> Date: Wed, 3 Jun 2015 17:44:20 +0200
>> Subject: [PATCH] gnu: Add BioPerl.
>>
>> * gnu/packages/bioinformatics.scm (bioperl-minimal): New variable.
>
> [...]
>
>> +(define-public bioperl-minimal
>> + (package
>> + (name "bioperl-minimal")
>
> So is it meant to be used as a Perl library, as a standalone executable,
> or both?
It's a library and a collection of perl executables using the library,
so I suppose "bioperl-minimal" would be appropriate?
>> + (native-search-paths (list (search-path-specification
>> + (variable "PERL5LIB")
>> + (files '("lib/perl5/site_perl")))))
>
> Why is it needed? At first sight it looks wrong because PERL5LIB is
> “owned” by Perl itself.
>
> If there’s an executable that needs to find the libs listed in
> ‘propagated-inputs’, the best way would be to use ‘wrap-program’, I
> think.
That's for the executables to find the library contained in this package
as well as the propagated Perl libraries. There are *many* executables,
which made me shy away from wrapping each of them to be run with the
PERL5LIB variable set.
~~ Ricardo
next prev parent reply other threads:[~2015-06-06 17:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 15:53 [PATCH] Add (minimal) BioPerl Ricardo Wurmus
2015-06-03 16:00 ` Andreas Enge
2015-06-04 16:19 ` Ludovic Courtès
2015-06-04 21:37 ` Pjotr Prins
2015-06-06 17:48 ` Ludovic Courtès
2015-06-06 17:52 ` Ricardo Wurmus [this message]
2015-06-06 18:05 ` Ludovic Courtès
2015-06-17 13:24 ` Ricardo Wurmus
2015-06-21 21:04 ` Ludovic Courtès
2015-07-21 8:41 ` Ricardo Wurmus
2015-07-21 9:24 ` Eric Bavier
2015-08-24 13:03 ` Ricardo Wurmus
2015-08-25 21:44 ` 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=87d218wwp9.fsf@mdc-berlin.de \
--to=ricardo.wurmus@mdc-berlin.de \
--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.