ports/180340: Mk/bsd.perl.mk -- r320679 breaks backwards compatibility

[Jeremy Chadwick]

>Number:         180340
>Category:       ports
>Synopsis:       Mk/bsd.perl.mk -- r320679 breaks backwards compatibility
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jul 06 04:40:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator:     Jeremy Chadwick
>Release:        FreeBSD 9.1-STABLE amd64
>Organization:
>Environment:
System: FreeBSD icarus.home.lan 9.1-STABLE FreeBSD 9.1-STABLE #0 r252769: Fri Jul 5 02:42:26 PDT 2013 root at icarus.home.lan:/usr/obj/usr/src/sys/X7SBA_RELENG_9_amd64 amd64
>Description:
	I talked about this issue on freebsd-ports late last month.  Please
	read the post for full details:

	http://lists.freebsd.org/pipermail/freebsd-ports/2013-June/084557.html

	The scope of impact is described further here:

	http://lists.freebsd.org/pipermail/freebsd-ports/2013-June/084561.html

	After a heated discussion (understandably so), where I was more
	or less told (but I'm still not entirely certain) "too bad", I
	came up with a very obvious/clean patch for the issue described:

	http://lists.freebsd.org/pipermail/freebsd-ports/2013-June/084569.html

	The reason I'm filing this PR is because I made mental note that
	if I didn't receive a response from bapt@ (particularly with regards
	to the patch) within 7 days I would file a PR for tracking purposes
	so that things didn't get lost in the chaos (easy to do/forget given
	the volume of responsibilities!)
>How-To-Repeat:
	See posts mentioned above; step-by-step instructions are there, or
	also here:

	http://lists.freebsd.org/pipermail/freebsd-ports/2013-June/084565.html
>Fix:
	Patch provided here:

	http://lists.freebsd.org/pipermail/freebsd-ports/2013-June/084569.html

>Release-Note:
>Audit-Trail:
>Unformatted: