On Mon, Apr 02, 2007 at 07:37:49PM +0200, Xavier Hanin wrote: > >The only feasible workaround would be to set the longfile attribute > >of the tar task to "gnu", but then you end up with a non-portable > >tarball, i.e. only extractable by GNU tar.
I just noticed that actually paths of up to 256 characters should be possible for regular files and directories in the standard USTAR format: http://www.opengroup.org/onlinepubs/009695399/utilities/pax.html#tagtcjh_15 (well, it's a little bit hackish, since the name may have up to 100 characters, but there's an additional prefix field that may be used to prepend up to 155 characters and a slash) The question is what ant creates for entries that fit into the USTAR scheme (155 + 1 + 100 characters) when using longfile="gnu" or defaults to "warn". [...] > So, should we prefer one of the option preserving standard tar format > (truncate, or omit) meaning that everybody using the tar version would have > problems with the javadoc and test reports, or a gnu version, meaning that > people with non gnu tar version wouldn't be able to untar our distrib? I'd go with the default. I'll see wether non-GNU tar/pax can cope with the file created by ant when you've done the release ;-) If ant uses the GNU exension even if USTAR would fit, the tar task of ant should be improved. In the meantime, people would have to install GNU tar as a workaround or just use the .zip release. Ciao, Kili -- >Nein, mein Gedächtnis ist manchmal wie ein... Wie heißt noch dieses >Gerät, durch das man Reis abgießt? Kochbeutel?
