From: "Jeff Trawick" <[EMAIL PROTECTED]>
Sent: Thursday, March 29, 2001 6:43 PM
> "William A. Rowe, Jr." <[EMAIL PROTECTED]> writes:
>
> > Why not simply
> >
> > #!perl
> >
> > to give them a clue where to start hunting :-?
>
> I don't get your point.
Sorry... are they looking to fix it since it's 'broke'? Is it sh, bash, perl
or what? On some 'workalikes' they may simply need to fix the path, on others
(strongly typed shebang paths) they need to edit it. Either way, I just though
#!perl would be clearer than #! when the build script doesn't find a perl
