[Xastir] User-visible change to build system.

[Tom Russo]

Thanks to Carl Makin for tracking down the issue where Xastir's build was
failing with recent versions of automake.

Turns out that our scripts directory improperly used some automake variables
in a way that was silently accepted in earlier versions of automake, but is
flagged as an error in recent versions.  Carl provided a fix for this, and
his fix has been applied to CVS.

The most noticable effect for users of Xastir built from CVS code is that now
scripts will be getting installed in /usr/local/share/xastir/scripts instead
of /usr/local/lib/xastir.

If you do a cvs update and install Xastir, scripts will now be in the new
location, and all Xastir-installed files will be under /usr/local/share/xastir
(other than the binaries, of course), rather than split between 
/usr/local/share/xastir and /usr/local/lib/xastir.

Once you update Xastir from CVS and confirm that the new scripts are installed
in /usr/local/share/xastir/scripts, you should remove /usr/local/lib/xastir
(sudo rm -rf /usr/local/lib/xastir), because the build procedure will not clean
out the old directories.  Leaving them there could be a source of confusion
later on, when scripts are changed -- the ones in /usr/local/lib/xastir will
be outdated.


-- 
Tom Russo    KM5VY   SAR502   DM64ux          http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236        http://kevan.org/brain.cgi?DDTNM
"And, isn't sanity really just a one-trick pony anyway? I mean all you get is
 one trick, rational thinking, but when you're good and crazy, oooh, oooh,
 oooh, the sky is the limit!"  --- The Tick