On Saturday, March 15, 2014 10:48 PM, Thomas Dickey <[email protected]> wrote:
> I see. I had tested this by setting umask in the build process,
> but using a pristine tarball (which would have correct permissions).
> I did that for both dpkg and rpm...
The source tarball does have the correct file permissions, but, when
extracting files, GNU tar will consider the user's current umask value
when setting a file's permissions instead of using only the mode-bits
in the tarball.
Speaking of tarballs, lynx2.8.8rel.2.tar has a couple of extraneous
files:
-rw-r--r-- dickey/lynx 0 2014-03-10 03:13 lynx2-8-8/test/nobody
-rw-r--r-- dickey/lynx 0 2014-03-10 03:13 lynx2-8-8/test/X
> > and add a couple of additional commands in there--something along the lines
> > of:
> >
> > find $(DOCDIR) -type d -print0 | xargs -0 chmod 755
> > find $(DOCDIR) -type f -print0 | xargs -0 chmod 644>
> something like (but not exactly: the example given isn't portable)
I presume `find $(DOCDIR) -type d -exec chmod 755 {} \;' is more
POSIX compliant?
Thanks,
Rajeev
_______________________________________________
Lynx-dev mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lynx-dev
