Wheen I replaced the non-portable "#!/usr/bin/perl" with the portable
"#!/usr/bin/env perl" I neglected the fact that some scripts have a -w
or -W argument after the command. This can't work with env, and the
correct approach is to put "use warnings;" in the script instead.
A lot of scripts in this directory had "#!/usr/bin/perl" hard coded at
their tops. This is wrong, because perl may not be installed
there (it isn't on a lot of non-Linux systems). I have replaced the
hard-coded path with "/usr/bin/env perl" which will locate the perl
binary in the user's PATH.
Some scripts in this directory already had that. Those are scripts
that I actually use myself on a system that has perl in
/usr/local/bin, and so I had already fixed them.
Another alternative to using /usr/bin/env would be to create a
configure test to find the perl binary, then substitute it in a .in
version of the script. That is more work, for negligible benefit.
CVS keywords such as "$Id$" no longer serve any purpose now that we're
using git, and need to be removed. This commit removes all of the
"$Id$" keywords, and a few other CVS keywords of no current value.
I also had to change some lines of the scripts/lang*.pl files that were
looking for $Id$ tags in their input and replacing them with comments.
The entire intent of this was to add two lines of comments to the top of
the output, and now it just does that, instead of depending on the
presence of the $Id$ keyword.
input. Eventually plan to have this script write a log file
containing objects so that Xastir can plot each of the positions.
This will be useful in quickly determining which of the formats is
within the area of interest. Developed this for Search & Rescue
applications.
