Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of admin@yacy-forum.de designates
 213.203.199.73 as permitted sender)
Message-ID: <42E8DBE4.1000703@yacy-forum.de>
Date: Thu, 28 Jul 2005 15:21:40 +0200
From: Roland Ramthun <admin@yacy-forum.de>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
MIME-Version: 1.0
To: Ant Developers List <dev@ant.apache.org>
Subject: Re: Bug in tar-section
References: <42E8B09E.8000702@yacy-forum.de> <42E8D04F.8040201@apache.org>
 <42E8D715.2080607@yacy-forum.de> <42E8D8DF.5060505@apache.org>
In-Reply-To: <42E8D8DF.5060505@apache.org>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit

Peter Reilly schrieb:
> From the ant manual:
> "Early versions of tar did not support path lengths greater than 100
> characters. Modern versions of tar do so, but in incompatible ways. The
> behaviour of the tar task when it encounters such paths is controlled by
> the /longfile/ attribute. If the longfile attribute is set to |fail|,
> any long paths will cause the tar task to fail. If the longfile
> attribute is set to |truncate|, any long paths will be truncated to the
> 100 character maximum length prior to adding to the archive. If the
> value of the longfile attribute is set to |omit| then files containing
> long paths will be omitted from the archive. Either option ensures that
> the archive can be untarred by any compliant version of tar. If the loss
> of path or file information is not acceptable, and it rarely is,
> longfile may be set to the value |gnu|. The tar task will then produce a
> GNU tar file which can have arbitrary length paths. Note however, that
> the resulting archive will only be able to be untarred with GNU tar. 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."
> 
> The tar page that Steve pointed out shows that there is a new posix tar
> format that will be used
> by gnu tar in the future - ant will probally support that then.

Ok, that answers my question.

Thank you.
Roland

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