Porter's Handbook Perl section update

[Chris Rees]

On 23 May 2012 21:25, Warren Block <wblock at wonkity.com> wrote:
> On Wed, 23 May 2012, Chris Rees wrote:
>
>> On 23 May 2012 18:11, Warren Block <wblock at wonkity.com> wrote:
>>>
>>> The second note in the Using perl section of the Porter's Handbook was
>>> unclear to me:
>>>
>>>  Note: It is recommended to avoid using ${SITE_PERL} as a dependency
>>>  listing. This is problematic because it means that bsd.perl.mk must be
>>>  included to satisfy the dependency. Additionally, if the module's files
>>>  change, it would require changing all dependent ports.
>>>
>>> After some talking with jgh@, I've suggested this:
>>>
>>>  Do not use ${SITE_PERL} in dependency declarations.  Doing so
>>>  assumes that bsd.perl.mk has been included, which is not always true.
>>>  Ports depending on this port will have incorrect dependencies if this
>>>  port's files move later in an upgrade.  The right way to declare Perl
>>>  module dependencies is shown in the example below.
>>>
>>> The second sentence is a little weak, but overall this makes much more
>>> sense, to me at least.  If this looks okay, I'd like to update the
>>> Porter's
>>> Handbook.
>>
>>
>> [adding perl@]
>>
>> Please!
>
>
> (Taking that as "please go ahead" rather than "please go away".)
>
> The attached diff replaces that note, cleans up some use of commas and minor
> wording, and removes <literal> tags around "Perl" when talking about the
> language rather than the specific interpreter. Capitalization is also
> changed as in
> http://learn.perl.org/faq/perlfaq1.html#Whats-the-difference-between-perl-and-Perl-
>
> I tried this with <application> tags around every instance of Perl, and
> reading it was like listening to someone who Pronounces Capitals.  One use
> of <application> in the title seems adequate.

Looks great to me.

Personally I would not have minded loads of <application>s, but that's just me.

Chris