On 4/3/07, Steve Loughran <[EMAIL PROTECTED]> wrote:
Stefan Bodewig wrote: > On Mon, 2 Apr 2007, Matthias Kilian <[EMAIL PROTECTED]> wrote: > >> I just noticed that actually paths of up to 256 characters should >> be possible for regular files and directories in the standard USTAR >> format: >> >> http://www.opengroup.org/onlinepubs/009695399/utilities/pax.html#tagtcjh_15 > > Maybe, but this is not supported by Ant (nobody wanted to contribute a > patch ;-) Or write the tests, more to the point. Xavier, -the only people who will complain about tar skipping files will be people on sysv unixes - Solaris, AIX, HPUX. The problem is that they wont notice at unpack time, but some time later when they try to build your app, or browse the javadocs, and find missing files.
Yes, but if we provide a disclaimer, we can hope people will use gtar or the zip distribution as Stefan suggests? -you can always *not* ship a tar file, give everyone a zip file, but set
the permissions on the zipfilesets so that if you unzip with the linux port of zip then anything marked as executable gets the exe bit set. As everyone with a JDK has the jar command, you can be sure that all recipients will be able to expand it somehow.
We don't even have the executable problem, since Ivy ships with absolutely no executable file for the moment. Ivy has always been shipped in zip format only, so my first idea was to continue like that. But if some users prefer tar.gz version, and if most of them have access to a gnu tar command, then it's not much work to ship this tar.gz version. I only hope people will read the disclaimer about gnu tar before complaining they are not able to read the javadoc or build from source... To conclude I think I'll add the gnu tar.gz distribution format and the disclaimer unless you tell me we should really prefer shipping only a zip version. I'm doing izpack installers @ work right now...there you create a JAR
containing 'packs', which can include zip files that are expanded at install time. I'm trying to get my individual components to publish their source, javadoc and jar files to ivy, then have a release project that pulls them all in, feeding them to izpack. If I can get it working, it will be a very nice process for packaging our redistributables.
Yes, indeed, and a nice use case of Ivy :) - xavier -- Learn Ivy at ApacheCon: http://www.eu.apachecon.com/ Manage your dependencies with Ivy! http://incubator.apache.org/ivy/
