Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 12464 invoked from network); 6 Apr 2006 04:49:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 6 Apr 2006 04:49:42 -0000 Received: (qmail 48841 invoked by uid 500); 6 Apr 2006 04:49:39 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 48742 invoked by uid 500); 6 Apr 2006 04:49:39 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 48731 invoked by uid 99); 6 Apr 2006 04:49:38 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Apr 2006 21:49:38 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of hari.developer@gmail.com designates 64.233.184.226 as permitted sender) Received: from [64.233.184.226] (HELO wproxy.gmail.com) (64.233.184.226) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Apr 2006 21:49:37 -0700 Received: by wproxy.gmail.com with SMTP id i4so56111wra for ; Wed, 05 Apr 2006 21:49:17 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=Kg/RANmgM+DcNNoGLeW6AF4q4LhSnhlxiSLvKWhH1v/zAD8g+eFI4S5ctFf4Mi9eBMld+1LyDuCcYhnZNfZluNJ/dPlgNbOstlc+rDwYYVdjShYmYuQtc4e3EyEF2XQExuPPxMKpzJbR2SlQbtI6Zc/fW5/p8Ru03DVIvxrMxV8= Received: by 10.54.122.17 with SMTP id u17mr256665wrc; Wed, 05 Apr 2006 21:49:17 -0700 (PDT) Received: by 10.54.123.13 with HTTP; Wed, 5 Apr 2006 21:49:16 -0700 (PDT) Message-ID: <80f34f3d0604052149r69fe6d71ibeea166fc561758d@mail.gmail.com> Date: Thu, 6 Apr 2006 10:19:16 +0530 From: "Hariharasudhan R" To: "Jakarta Commons Developers List" Subject: Re: [compress] Interface is ready In-Reply-To: <44342F39.9060405@possessed.de> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_8274_7275940.1144298956562" References: <442D3C42.3030901@possessed.de> <6bde122b0604021248r3eaae4ech4fa76b33dcde3018@mail.gmail.com> <44322DF5.5000209@possessed.de> <80f34f3d0604050927n10921023oa504ae9489405617@mail.gmail.com> <44342F39.9060405@possessed.de> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_8274_7275940.1144298956562 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi Chris, The only information that I was able to find that said anything useful abou= t the difference is found in this page. http://java.sun.com/products/archive/j2se/1.2.2_017/install-docs.html Snippet from this page (you'll find it at the bottom of the page) : "Background: The original tar format supports a maximum path size of 99 characters. If you use Solaris tar, you will not see a problem, because Solaris tar extends this format beyond 99 characters but in a Solaris-only way. GNU tar has a different way of extending the format, so is incompatibl= e with the Solaris tar. WinZip and Cygnus GNU tar 1.11.8 do not support the Solaris way. We recommended that you use Solaris tar to extract the archive= , or use the jar tool or WinZip to extract the zip version." >> Note : WinRAR seems to work properly with Solaris tar archives, though.. I am trying to get docs on the tar implementation in Solaris. I will get back once I get more information. What's happening is that for files with long path size , they get extracted as if they were present in the root directory. I am very much interested in a version that works on Solaris. I dont know i= f I'll have time to work right now on a Solaris tar implementation, but if someone gets around to writing one I'll surely be able to help test it. You could also try installing Solaris on x86 for testing, since it is free. Thanks, Hari. On 4/6/06, C. Grobmeier wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > > Does this work with Solaris tar, since Solaris tar is different from GN= U > tar > > ? > > If not , is there a plan to do so ? > > Won't making TarEntry an interface with Solaris/GNU implementations be = a > > good idea ? > > This is just an idea off the top of my head.. I've not delved too much > into > > the code.. > > i have just used the old APIs which have been implemented bevor ages. > In the old testcases [1] i see that there seem to be a difference > between Posix Tar and GNU Tar. Is this what you meant? It seems there is > work to do left. I am sorry that i am not to deep into tar yet. If you > have documents for me to read just send me the urls. > > Thanks, > Christian > > > [1] org.apache.commons.compress.TarTestCase.java > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2.1 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFENC85kv8rKBUE/T4RAvepAJ9UhbEJ/L1CfQnz42Z3zyMgBQXFOwCfXDxV > BHUXlp3lDBNsE4bgTUFOfMU=3D > =3DoVNZ > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org > For additional commands, e-mail: commons-dev-help@jakarta.apache.org > > ------=_Part_8274_7275940.1144298956562--