svn commit: r355497 - in head: Mk/Uses lang lang/perl5.14 lang/perl5.16 lang/perl5.18 lang/perl5.20 lang/perl5.20/files

[Adam McDougall]

On 07/23/2014 08:59, Mathieu Arnold wrote:
> 
> 
> +--On 23 juillet 2014 08:41:47 -0400 Adam McDougall <mcdouga9 at egr.msu.edu>
> wrote:
> | On 05/27/2014 08:19, Mathieu Arnold wrote:
> |> Author: mat
> |> Date: Tue May 27 12:19:24 2014
> |> New Revision: 355497
> |> URL: http://svnweb.freebsd.org/changeset/ports/355497
> |> QAT: https://qat.redports.org/buildarchive/r355497/
> |> 
> |> Log:
> |>   Add perl 5.20.0.
> |>   
> | 
> | Is the removal of the /usr/bin/perl option intentional?  If so, should
> | there be an entry in UPDATING?  It tripped me up when I upgraded.  Thanks.
> 
> Yes, it was.  I admit I forgot about the UPDATING entry, as the ports tree
> already take care of making sure the shebang are corrects.
> 
> Perl was removed from the base system more than ten years ago, it should
> have been long enough for everybody to fix their local scripts... :-)
> 

I am okay with the change as long as it is communicated since this
removed an option that was on by default, not just disabling it.
Leaving my scripts as /usr/bin/perl made them easier to share with other
platforms, so I had no good reason to change my scripts.  I can use
#!/usr/bin/env perl as long as my PATH is set sufficiently, which is not
always the case in cron.