[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Outdated help2man; avoiding needing to "build" help2man.pl
From: |
Pavel Roskin |
Subject: |
Re: Outdated help2man; avoiding needing to "build" help2man.pl |
Date: |
Mon, 1 Oct 2012 16:20:01 -0400 |
On Thu, 13 Sep 2012 14:51:53 -0700
Don Armstrong <address@hidden> wrote:
> In stepmake/stepmake/help2man-rules.make, I ran across the following:
>
> # We must invoke the generated $(outdir)/help2man script instead of
> # the help2man.pl source, which means that the scripts/build directory
> # must be built first.
> #
> # From the perlrun man-page:
> #
> # If the #! line does not contain the word "perl", the
> # program named after the #! is executed instead of the Perl
> # interpreter. This is slightly bizarre, but it helps
> #
> # Indeed it is. Perl sucks.
> #
> # Two screenfulls explaining that the otherwise standard #! is broken
> # for perl, and arguing that this broken magic is better in some
> # cases. Four more explaining what a line comment is, and that it may
> # be parsed, same here.
>
> While it's correct, you can trivially work around this problem by
> changing
>
> address@hidden@ -w
>
> to
>
> address@hidden@ -w
> #! perl -w
Considering the subsequent discussion, it's probably irrelevant to
LilyPond. However, it's a bad idea to use an executable name without
full path. See
http://www.cyberciti.biz/tips/finding-bash-perl-python-portably-using-env.html
So it should be
#!/usr/bin/env perl -w
--
Regards,
Pavel Roskin
- Re: Outdated help2man; avoiding needing to "build" help2man.pl,
Pavel Roskin <=