[Xastir] Why scripts are not executable anymore Re: NWS get problem

[Tom Russo]

On Mon, Nov 26, 2012 at 06:25:24PM -0700, we recorded a bogon-computron collision of the <russo at bogodyn.org> flavor, containing:
> 
> And now that I look on *MY* system, NONE of the scripts in 
> /usr/local/share/xastir/scripts have the execute permission set.
> Did our install process *ever* set execute permission on these scripts before?
> I can't think of anything that has changed recently to undo that.

Yes, I can.

Back in February I was forced to change scripts/Makefile.am because new 
versions of Automake refuse to accept certain combinations of instructions
like "pkglib_SCRIPTS" which once sent our scripts to /usr/local/lib/xastir --
It was always the case that only certain prefixes were intended to be used
with _SCRIPTS, but older versions of automake let it slide quietly when they
were misused.  These days "pkglib" is an illegal use for the _SCRIPTS primary,
and current versions of automake refuse to proceed.

This had to be changed just to get it to work, but with the side effect that
the scripts are now being installed as data instead of as scripts... i.e. 
they're not executable on install.  

This will obviously need to be fixed.  It may take some time to figure out
the correct Automake invocation to get it right.  It might require yet another
relocation of the scripts.  Grumble.

For now, just do a chmod u+x on the files in /usr/local/share/xastir/scripts.

-- 
Tom Russo    KM5VY   SAR502   DM64ux          http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236        http://kevan.org/brain.cgi?DDTNM
 echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]