Date: Wed, 07 Mar 2007 08:59:16 -0800 From: Tim Kientzle <kientzle@freebsd.org> To: Jim Rees <rees@freebsd.org> Cc: Greg 'groggy' Lehey <grog@freebsd.org>, cvs-src@freebsd.org, src-committers@freebsd.org, Ruslan Ermilov <ru@freebsd.org>, cvs-all@freebsd.org Subject: Re: cvs commit: src/usr.sbin/pkg_install/lib url.c Message-ID: <45EEEF64.1010006@freebsd.org> In-Reply-To: <20070307132248.GA9276@citi.umich.edu> References: <200703061454.l26Esj7D043245@repoman.freebsd.org> <45EDA7E2.4040300@freebsd.org> <20070306204307.GD43608@rambler-co.ru> <20070306231228.GC68567@wantadilla.lemis.com> <45EE3BC4.8070309@freebsd.org> <20070307132248.GA9276@citi.umich.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Jim Rees wrote: > I'm not convinced this fix is correct. I don't think tar ever did this > before gnu came along, You're dating yourself here, Jim. GNU tar is over 20 years old. ;-) I also thought gnu tar shipped with FreeBSD 1.0 in 1993, though I might be wrong about that. >... and I would find it surprising to have this option > turned on just because I'm root. And if you enable it automatically for > root, now you need another option to turn it off. Sad but true. The discussion in the Single Unix Standard rationale about the design of the "-p" option for pax should be required reading for anyone interested in the design of archivers. Unfortunately, an awful lot of build scripts for various ports rely heavily on arcane details of gnu tar behavior. A lot of stuff would break if bsdtar didn't at least make an effort to follow GNU tar command-line conventions. Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45EEEF64.1010006>