On Sunday, March 16, 2014 8:49 PM, Thomas Dickey <[email protected]> wrote:
> On Sun, Mar 16, 2014 at 08:11:31AM +0800, Rajeev V. Pillai wrote: > > 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. > > I did say "pristine": packagers as a rule work directly from the tarball, > and the packaging systems generally (I don't know of exceptions) don't > alter the permissions. I'm not clear about what you mean by pristine in this context--I build most of my binaries directly from the tarballs (in the usual manner): 1. Download source tarball. 2. Extract tarball. 3. ./configure ... 4. make 5. make install (as root) My understanding is that unless steps 2-5 are executed as root (ie. not only step 5.), the owner & permissions for share/lynx_doc/* will not be set correctly. Are packaging systems run under a specific umask (0022, say) and with a specific user like root? > > 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 > > those are intentional: > > 2014-03-09 (2.8.8rel.2) > * correct errata in test-files which cause broken links in break-out directory > in lynx.isc.org server -TD Ah, I see! I was confused by the addition of 2 oddly named zero-length files in lynx_doc/test/. Thanks, Rajeev _______________________________________________ Lynx-dev mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lynx-dev
