unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: 27282@debbugs.gnu.org
Subject: bug#27282: Perl 5.26.0 "dotless @INC" [was Re: bug#27227: [PATCH] gnu: perl: Update to 5.26.0.]
Date: Wed, 7 Jun 2017 18:37:30 -0400	[thread overview]
Message-ID: <20170607223730.GA4844@jasmine> (raw)
In-Reply-To: <20170604191939.GB2840@jasmine>

[-- Attachment #1: Type: text/plain, Size: 1341 bytes --]

On Sun, Jun 04, 2017 at 03:19:39PM -0400, Leo Famulari wrote:
> > >> Leo Famulari <leo@famulari.name> writes:
> > >> 
> > >> > * gnu/packages/perl.scm (perl): Update to 5.26.0.
> > >> > * gnu/packages/patches/perl-no-sys-dirs.patch: Update patch context for
> > >> > 'hints/linux.sh'.
> 
> I merged master into core-updates and pushed this as
> f65805485dac3f8c4586648e3f7e901202095a19.

Building locally, I found that SWIG fails to build with this new Perl
release due to the removal of the current directory from @INC. This
change is mentioned in the Perl release notes:

"We removed the current directory from @INC

We consider this a security change, and although it might cause
discomfort to some users, we had to do it. Both Perl 5 Porters and the
Toolchain Gang put effort into easing the transition to a dot-less
@INC.

If you want to load a module from the current directory, you can still
do this in one the following ways:

[...]

# Use the environment variable
PERL_USE_UNSAFE_INC=1"

http://blogs.perl.org/users/sawyer_x/2017/05/perl-5260-is-now-available.html

It doesn't look like this has been addressed by the SWIG maintainers
yet.

We should set this PERL_USE_UNSAFE_INC variable in the SWIG package
definition, right? Probably we will need to set it in several other
packages as well.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

       reply	other threads:[~2017-06-07 22:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <dc032780692ec6297409325f3b8534d7add2cea2.1496565624.git.leo@famulari.name>
     [not found] ` <87k24ryigh.fsf@fastmail.com>
     [not found]   ` <20170604163721.GC14880@jasmine>
     [not found]     ` <87inkbppmb.fsf@fastmail.com>
     [not found]       ` <20170604191939.GB2840@jasmine>
2017-06-07 22:37         ` Leo Famulari [this message]
2017-06-08  0:25           ` bug#27282: Perl 5.26.0 "dotless @INC" Leo Famulari
2017-06-08 12:28           ` bug#27282: Perl 5.26.0 "dotless @INC" [was Re: bug#27227: [PATCH] gnu: perl: Update to 5.26.0.] Ludovic Courtès
2017-06-08 15:29             ` Leo Famulari
2017-06-12  2:48               ` Leo Famulari
2017-06-13 19:47                 ` Leo Famulari
2017-06-14  7:38                   ` Ludovic Courtès
2017-06-14 14:30                     ` Leo Famulari
2017-08-02 22:10                       ` Ludovic Courtès
2017-08-02 22:41                         ` Leo Famulari

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=20170607223730.GA4844@jasmine \
    --to=leo@famulari.name \
    --cc=27282@debbugs.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 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).