Re: [Lynx-dev] non-executable files in scripts/ (when upgrade with patches)

[Thomas Dickey]

On Wed, 1 Feb 2006, Atsuhito Kohda wrote:

> Hi all,
>
> I've maintained lynx-cur and with 2.8.6dev.17 there seemed
> a bit problems.  I've updated source trees of lynx by patches
> and got an error at compiling 2.8.6dev.17 because scripts/cfg_path.sh
> was not executable.

ok.  I should use $(SHELL) as a prefix in the makefile to work around 
this.  The usual reason for doing that is to work around one of the 
limitations of CVS (it doesn't preserve permissions - or timestamps).
Some packagers have complained when I have scripts that rely on the
permissions since they check the distribution into CVS.

However, the scripts in the tarball are executable since that's the way 
the permissions are defined.

Using patch, there is no way that I know to propagate the permissions in 
this way.  (I had thought most packagers started from a tarball rather 
than using patch - but then see above for CVS limitations).

> I downloaded full source then it seemed all files in scripts
> directory were executable.
...
> Is there any chance that even with a patch, one could get
> correct permission of files?

It would be safe to do this:

        find . -type '*.sh' -exec chmod u+x {} \;

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net