ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 15230] - TAR long path names (GNU format) append a trailing 0 char
Date Wed, 11 Dec 2002 03:03:53 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15230>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15230

TAR long path names (GNU format) append a trailing 0 char





------- Additional Comments From jdb@getsu.com  2002-12-11 03:03 -------
By the way, I noticed a few discrepencies between the output of ant's tar and
GNU tar.  Most involve whitespace or leading zeros, but the one I'm a little
worried about is the 0 char terminators on header fields.  The header fields are
fixed length.  Ant's tar will use the whole field width; altho it will pad any
remaining bytes with 0, it will not include a terminating 0 byte if the data
fills the field.  On the other hand, GNU tar includes a terminating 0 byte (and
one less byte of data in that field).

Of course, the risk is for some tar program to assume that the header fields are
terminated with a 0 byte.  C programs often make such assumptions about strings.
 It might even be in the tar spec, altho I don't know where "the" tar spec is.

However, this is not the problem at hand.  "If it ain't broke, don't fix it."

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message