ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 8981] - Tar task command additional features
Date Sat, 11 May 2002 16:39:28 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8981>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8981

Tar task command additional features





------- Additional Comments From donkeeting@yahoo.com  2002-05-11 16:39 -------
1. Yes, I agree that this could be done, but there are situations where this is
not pratical, or efficient.  Example: Suppose you have an existing directory
structure containing many files, and you have a tar file which might contain
some of the same files and some new files.  Suppose you would like to know the
contents of the tar file.  If you untar the file, you will not be able to tell
which files came from the tar, and which files were preexisting, or both.
A nice feature would be to have the ability to do the equivilant of the tar
command: "tar -tvf tarfile.tar" or "tar -tf tarfile.tar".  I would like to be
able to make the table of contents available.


2. In version 1.4.1, if I use this:
<tar tarfile="${build.dir}/listfile.tar" basedir="${src.dir}"
includesfile="listfile.txt" />
where "listfile.txt" is contained in the basedir, and the file contains
filenames separated by newlines, it will tar all of the files from the list.
The problem is, in my case the basedir will be the root directory, so I need to
be able to include the list of fully qualified paths of files to be included in
the tar file.

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


Mime
View raw message