Return-Path: 
 <ant-dev-return-30656-qmlist-jakarta-archive-ant-dev=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-dev-archive@apache.org
Received: (qmail 31263 invoked from network); 20 Apr 2002 03:01:52 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 20 Apr 2002 03:01:52 -0000
Received: (qmail 21188 invoked by uid 97); 20 Apr 2002 03:01:59 -0000
Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org
Received: (qmail 21172 invoked by uid 97); 20 Apr 2002 03:01:59 -0000
Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:ant-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:ant-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:ant-dev-help@jakarta.apache.org>
List-Post: <mailto:ant-dev@jakarta.apache.org>
List-Id: "Ant Developers List" <ant-dev.jakarta.apache.org>
Reply-To: "Ant Developers List" <ant-dev@jakarta.apache.org>
Delivered-To: mailing list ant-dev@jakarta.apache.org
Received: (qmail 21161 invoked from network); 20 Apr 2002 03:01:59 -0000
Message-ID: <001f01c1e817$b4e171d0$a800a8c0@CurtMicron>
From: "Curt Arnold" <carnold@houston.rr.com>
To: <ant-dev@jakarta.apache.org>
Subject: compression for tar/untar (resend)
Date: Fri, 19 Apr 2002 22:01:40 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_001C_01C1E7ED.C8E7BBA0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

------=_NextPart_000_001C_01C1E7ED.C8E7BBA0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I've checked the mailing list archive and bugzilla and was surprised to =
find no discussion on adding compression options to the tar and untar =
tasks.

Currently to create a compressed tar file, you can use a <tar> task =
followed by a <gzip> or <bzip2> tasks.  While that works, it requires =
sufficient disk space for the intermediate tar file which may be =
inconvenient when working for extremely large archives.

It would seem to be fairly simple to add a compress attribute with =
acceptable values of "none", "gzip" and "bzip2" to the tar and untar =
tasks to enable them to create or expand tar.gz or tar.bz files in one =
step.



 =20

------=_NextPart_000_001C_01C1E7ED.C8E7BBA0--