Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 9 Jan 2012 18:58:35 +0000
From:      Chris Rees <crees@freebsd.org>
To:        Ruslan Mahmatkhanov <cvs-src@yandex.ru>
Cc:        FreeBSD Ports Mailing List <ports@freebsd.org>, perl@freebsd.org, skv@freebsd.org
Subject:   Re: Perl symlinks question
Message-ID:  <CADLo839GMbxbkL=j7XjEGfgveJkDHOmkD5P0nyW3kOjaJQfi2Q@mail.gmail.com>
In-Reply-To: <4F0B36BD.8070202@yandex.ru>
References:  <4F0B36BD.8070202@yandex.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
Adding perl and skv@

On 9 January 2012 18:49, Ruslan Mahmatkhanov <cvs-src@yandex.ru> wrote:
> Hi.
>
> There is PR: http://bugs.freebsd.org/163687
> It tries to fix port building when user built it's perl installation with
> USE_PERL option (creating symlinks in /usr/bin) set to off (not the
> default). Patch in PR just replaces static shebang with ${PERL} variable
> from Mk/bsd.perl.mk. But it doesn't actually fix the build, because
> consequent call of aclocal-1.11 will fail since it's shebang set to
> '/usr/bin/perl' too.
>
> The question is how to properly handle this PR:
> 1. Fix devel/automake too (by replacing /usr/bin/perl with ${PERL})
> 2. Create symlinks unconditionally in perl port and drop USE_PERL option
> 3. Close PR as invalid since the build fails because of user
> =9A intervention (changing the value of default option)
>
> Thanks.
>
> As for me, i believe second option is more preferable, but i don't know i=
f
> there something behind this.
>
> PS. I think patch attached (for bsd.perl.mk) should be considered since w=
e
> no more have perl in base. And i'd also exclude perl-5.6.* from CONFLICTS=
 in
> lang/perl*, because it's something so ancient and doubtful to face with.
>

I don't see any point in the symlink being optional either -- I vote for 2.

Chris



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo839GMbxbkL=j7XjEGfgveJkDHOmkD5P0nyW3kOjaJQfi2Q>