Re: Perl module build+install process

[Ludovic Courtès]

Tom Molesworth <address@hidden> skribis:

> On 11 Aug 2014 21:37, "Ludovic Courtès" <address@hidden> wrote:
>>
>> Tom Molesworth <address@hidden> skribis:
>>
>> > Since Perl uses an include path, much like the $PATH environment
> variable
>> > for finding executables, this seems to imply that you'd need every
> module
>> > added to the Perl include path (via $PERL5LIB). This would quickly
> become
>> > unwieldy as more modules are installed.
>>
>> Normally, ‘guix package --install’ and ‘guix package --search-paths’
>> would suggest adding ~/.guix-profile/lib/perl/... to $PERL5LIB, which
>> should solve the problem, no?
>
> If that means there's just a single extra PERL5LIB entry rather than one
> per installed module, yes - that should be fine.

Exactly.

> The output we'd seen looked like each module ended up in a separate path,
> but maybe we were misinterpreting, or a later step copies/symlinks to a
> common library path.

Well, ~/.guix-profile/lib/perl5 contains symlinks that make the union of
all the Perl packages installed in the user’s profile.

> Note that this is a separate concern to the install path not matching the
> final location of the files; the provided installation path at build time
> is used in some modules (XML::SAX in this case). Passing an installation
> path at build time, then moving the files afterwards, is likely to cause
> errors at runtime.

Files aren’t moved after installation.

Thanks,
Ludo’.