On Jan 20, 2007, at 5:25 PM, Salvatore Domenick Desiano wrote:
o I've never seen this before. Does anyone know what would cause this erroro on OS X?On Tiger, at least, gnutar and tar are the same program and don't actually seem to be gnutar (they lack many of the options).
On Tiger (10.4) tar is gnutar is GNU tar 1.14 (and supports --no-same- owner)
On previous versions of Mac OS X (I'm not sure if it was 10.3 and before or 10.2 and before) tar was bsd tar and there was also gnutar present.
So, ifsomeone has the gnutar port installed and ahead of /usr/bin, the port isgood to go. If not, you'll get the error you saw.
--no-same-owner isn't available everywhere (and macports base actually checks to see if it's available when building from source).
If a port really needs it when it is available, the portfile could probably look at tar_command from port_autoconf.tcl
-- Daniel J. Luke +========================================================+ | *---------------- [EMAIL PROTECTED] ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
