[Bug 205367] Multiple ports: PERL should be used instead of PERL5

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205367

--- Comment #8 from Chris Hutchinson <portmaster at bsdforge.com> ---
(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.