On 4/2/07, Matthias Kilian <[EMAIL PROTECTED]> wrote:
On Mon, Apr 02, 2007 at 06:41:03PM +0200, Xavier Hanin wrote:
> Do any of you know if it is a tar limitation or only an ant tar task
> limitation? Is there any workaround?
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.
Thanks, I should have read the task doc carefully, there is a whole
paragraph about this problem :)
As far as I understand, it seems that the default is to warn only, but it's
not clear to me if in this case the tar will be extractable by a non gnu
tar. From the task doc:
"The default for the longfile attribute is warn which behaves just like the
gnu option except that it produces a warning for each file path encountered
that does not match the limit"
So it seems that even with the default longfile option I'll get a non
standard tar. But I don't really know if it's important or not, I'm a
windows user, and even on *nix systems I often use the zip/unzip commands :)
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? 100
chars is not so long, do anybody else has ever faced this question? If it
was only I would only provide a zip anyway :-)
- Xavier
Ciao,
Kili
--
As a community, we should try to write stuff that is perfect.
Anything else is an utterly lame and pathetic cop-out.
-- Theo de Raadt
--
Learn Ivy at ApacheCon: http://www.eu.apachecon.com/
Manage your dependencies with Ivy!
http://incubator.apache.org/ivy/
