From: Eric Bavier <ericbavier@centurylink.net>
To: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>
Cc: guix-devel@gnu.org, Alex Sassmannshausen <alex@pompo.co>
Subject: Re: [PATCH] Wrap binaries in perl build system.
Date: Tue, 15 Nov 2016 22:39:15 -0600 [thread overview]
Message-ID: <20161115223915.5cb51d59@centurylink.net> (raw)
In-Reply-To: <20161112172446.5571-1-alex@pompo.co>
On Sat, 12 Nov 2016 18:24:45 +0100
Alex Sassmannshausen <alex.sassmannshausen@gmail.com> wrote:
> Hello,
>
> Perl, like Python and Guile, uses an environmental variable to make libraries
> accessible to binaries. For this purpose, binaries need to be wrapped with an
> executable which sets the env variable appropriately.
>
> This patch implements the same functionality that the Python build side code
> already has (I pretty much lifted it from there).
>
> This works nicely in my tests (a package I will submit once this has been
> merged).
>
> Comments welcome,
I don't recall specifically why this hasn't been done all along, but
IIRC there was some concern that, perl coming up in so many places as
it does, setting the perl environment variable at the application level
could adversely pollute the environments of packages farther down.
I don't know of any examples where this has actually caused problems,
however, so I'd support building a branch and seeing what happens.
2cents,
`~Eric
prev parent reply other threads:[~2016-11-16 4:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-12 17:24 [PATCH] Wrap binaries in perl build system Alex Sassmannshausen
2016-11-12 17:24 ` [PATCH] build-system/perl: Add wrap phase Alex Sassmannshausen
2016-11-13 12:23 ` Ludovic Courtès
2016-11-13 15:11 ` Hartmut Goebel
2016-11-13 20:05 ` Leo Famulari
2016-11-13 21:41 ` Hartmut Goebel
2016-11-16 4:39 ` Eric Bavier [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161115223915.5cb51d59@centurylink.net \
--to=ericbavier@centurylink.net \
--cc=alex.sassmannshausen@gmail.com \
--cc=alex@pompo.co \
--cc=bavier@member.fsf.org \
--cc=guix-devel@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.