Subject: Re: Binary packages with pax (PR pkg/25194)
To: None <tech-pkg@NetBSD.org>
From: James K. Lowden <jklowden@schemamania.org>
List: tech-pkg
Date: 04/18/2004 05:01:57
On Fri, 16 Apr 2004, Jim Bernard <jbernard@mines.edu> wrote:
> >   Currently gnustep-base (see PR pkg/25194) and other packages fail to
> >   
> > build correct binary packages on NetBSD.  The reason is a 100
> > character (full) path length limit that is exceeded in the PLISTs for
> > these packages.  It appears that when pax is used to create packages,
> > this limit is strictly enforced, truncating the corresponding path
> > names in the archive.

http://www.opengroup.org/onlinepubs/007908799/xcu/pax.html

I wonder, is our pax correct in this?  It looks like the path is formed by
prefix+name, for a total of up to 255 characters (cf. "Extended tar
Format").  There doesn't seem to be any rule preventing 'name' from
including slashes.  Perhaps that is the trick gtar is using.  

--jkl