On Fri, 13 Nov 2009, Holger Hans Peter Freyther wrote:
> On Thursday 12 November 2009 13:58:23 Robert P. J. Day wrote:
>
> > i'm checking right now if there's an option to "ls" to turn
> > *off* that feature, but i don't see one offhand. perhaps a better
> > lesson is that the way xterm's sinstall.sh script works is really
> > hacky, using sed to allegedly reproduce a file's existing mode
> > settings. perhaps there's a simpler way to get that effect
> > without dragging "sed" into it. but, again, if only one package
> > was affected, maybe just hack up an xterm fix and move on, and
> > deal with things on a case-by-case basis as they come up.
>
> Hi Robert,
>
> Could you please try this patch to the sinstall.sh?
>
> http://paste.lisp.org/display/90216
it looks like that patch was already applied, but that doesn't solve
the problem since the final numeric mode string still has that
trailing period that mucks things up.
as a simple fix that i've used before, i just added this to
sinstall.sh, at line 131:
PROG_MODE=`echo ".$cf_mode" | sed -e 's/^..//' -e 's/rw./7/g'
-e 's/r-./5/g' -e 's/---/0/g' -e 's/--[sxt]/1/g' -e 's/+//g'`
$trace "final PROG_MODE = ${PROG_MODE}" # prints "755."
PROG_MODE=${PROG_MODE%\.} <-- manually strip that period
$trace "really final PROG_MODE = ${PROG_MODE}" # prints "755"
and it works, i just tested that. so i'm not sure what that extended
sed expression was supposed to accomplish but it did nothing to solve
this issue.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================