From owner-freebsd-ports-bugs@freebsd.org Thu Dec 17 07:27:40 2015 Return-Path: Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A8C52A4A66D for ; Thu, 17 Dec 2015 07:27:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7EFA01579 for ; Thu, 17 Dec 2015 07:27:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id tBH7Re7k054496 for ; Thu, 17 Dec 2015 07:27:40 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 205367] Multiple ports: PERL should be used instead of PERL5 Date: Thu, 17 Dec 2015 07:27:39 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Ports Framework X-Bugzilla-Version: Latest X-Bugzilla-Keywords: needs-qa, patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: portmaster@bsdforge.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: portmgr@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2015 07:27:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205367 --- Comment #8 from Chris Hutchinson --- (In reply to Mikhail Teterin from comment #7) > (In reply to Kubilay Kocak from comment #5) > > with regard to all perl ports, not just those mentioned in this issue > > I'm still unclear, what the purpose of the PERL5-setting is -- and whether > the current implementation in perl5.mk actually serves that purpose. > > The comment inside the file states: > > # PERL5 - Set to full path of perl5, either in the system or > # installed from a port. > > If the comment accurately documents the intention, then the implementation > falls short -- it may set the variable incorrectly in a scenario I described. > > If the implementation is correct -- as Chris stated without elaborating -- > then the comment needs to be corrected to avoid future confusion by > maintainers of perl-using ports... Firstly; apologies, I misinterpreted your issue. This one reads *much* better -- for me, anyway. I haven't been able to duplicate what you've described happened to you, and while my development box tracks CURRENT, it is lagging about a month. Or because I still always use ${PERL5} ? Could an exp-run reveal this (the issue you describe)? I just checked out a copy of perl5.mk from HEAD. It's different enough from the one I'm currently using, that I going to take the time to perform a fresh install of CURRENT on one of the spares I have, and try and duplicate your described issue, tomorrow. I'll post back my findings either way. --Chris -- You are receiving this mail because: You are on the CC list for the bug.