[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [PATCH] Produce POSIX.1 compliant tarballs.

From: Ben Reser <ben_at_reser.org>
Date: 2004-03-11 08:35:07 CET

On Wed, Mar 10, 2004 at 09:44:30PM -0600, Travis P wrote:
> The tar man page on AIX had this to say about length (which is probably
> not news to you, but I thought it interesting -- the 255 limit not
> being a simple in-total limit):
> --
> When specifying path names that are greater than 100 characters for the
> United States Tape Archiver (USTAR) format, remember that the path name
> is composed of a prefix buffer, a / (slash), and a name buffer.
>
> The prefix buffer can be a maximum of 155 bytes and the name buffer can
> hold a maximum of 100 bytes. If the path name cannot be split into
> these two parts by a slash, it cannot be archived. This limitation is
> due to the structure of the tar archive headers, and must be maintained
> for compliance with standards and backwards compatibility. In addition,
> the length of a destination for a hard or symbolic link ( the 'link
> name') cannot exceed 100 bytes.
> --

Yup, the GNU tar documentation I pointed to explains this (although not
as clearly). This isn't a problem for us because currently our maximum
path is well under 155 chars. If we surpase 155 chars and the 155th
char isn't a / then we should get an error from cpio. In which case we
need to simply reconsider our directory structure. There is no portable
way to go beyond 155 chars without some hoop jumping in our pathnaming.

-- 
Ben Reser <ben@reser.org>
http://ben.reser.org
"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Mar 11 08:35:22 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.