unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Garlick <pgarlick@tourbillion-technology.com>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: 01/03: gnu: ikiwiki: Revert to standard wrapper.
Date: Tue, 02 Jun 2020 13:29:14 +0100	[thread overview]
Message-ID: <c61a81b75466fd5919f21fc1f252da5a5cf1dfab.camel@tourbillion-technology.com> (raw)
In-Reply-To: <87mu5l50r8.fsf@cbaines.net>

Hi Chris,

> I don't think there was ever a bug report for this, but I think I've
> found the IRC conversation for context:
> 
>   http://logs.guix.gnu.org/guix/2017-10-17.log#203630

Thank you for this link and taking a look at this patch.

I have been adding the missing inputs to ikiwiki.  In the process I
noticed that the cgi script needs a way of finding the perl
dependencies.  The Debian way of packaging the perl modules allows
ikiwiki to see its dependencies immediately.  In Guix, as you said, it
needs some help via PERL5LIB.

In using ikiwiki I found that I needed to add the PERL5LIB variable to
the setup file anyway, so that the cgi script can see extra modules
that are not needed at build time.  In my setup file there is an 'ENV'
section which contains: 

PERL5LIB: /home/paul/.guix-profile/lib/perl5/site_perl

This means that there is no need to have PERL5LIB in the wrapper. 
Instead the dependencies can be propagated in the normal way.  This
fits in with the PREREQ_PM section of ikiwiki's Makefile.PL.

So far,everything I have tested works as expected.  After the latest
commit 
e642f78f2eaf1d53d656ff3cd86d4dd186e8eb52 all the main tests pass.

Best regards,

Paul.






      reply	other threads:[~2020-06-02 12:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200601191735.15328.13392@vcs0.savannah.gnu.org>
     [not found] ` <20200601191737.45A2520A26@vcs0.savannah.gnu.org>
2020-06-02  8:26   ` 01/03: gnu: ikiwiki: Revert to standard wrapper Christopher Baines
2020-06-02  8:29     ` Christopher Baines
2020-06-02 12:29       ` Paul Garlick [this message]

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=c61a81b75466fd5919f21fc1f252da5a5cf1dfab.camel@tourbillion-technology.com \
    --to=pgarlick@tourbillion-technology.com \
    --cc=guix-devel@gnu.org \
    --cc=mail@cbaines.net \
    /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).