Ok, then leave .zip (+installer .jar) for the binary distro, and .zip and .tar.gz for the sources.
This is %50 a reduction and they can't get it wrong (i.e. no .tar.gz binary distro) I'd be also tempted to remove the .zip sources just to know what a user has downloaded by only looking at the extension. Windoze tools (winzip, etc.) can open .tar.gz anyway. > -----Original Message----- > From: Scott M Stark > Sent: 17 March, 2006 20:24 > To: Dimitris Andreadis; 'jboss-development@lists.sourceforge.net' > Cc: QA > Subject: RE: Simplifying the JBoss source/binary distributions > > This is what we had a long time ago but there was a request > for tar distributions. If it turns out that the old posix tar > implementations that for some reason have not been dropped > as the default platform tar(this problem is at least 15 years > old) cause problems for naïve users, perhaps we just need to > stick with what works. > > I doubt the source distributions are ever a problem. It is > the unpacked deployments with nested classes that trigger the > long path name requirement. > > > -----Original Message----- > > From: Dimitris Andreadis > > Sent: Friday, March 17, 2006 1:44 AM > > To: jboss-development@lists.sourceforge.net > > Cc: QA > > Subject: Simplifying the JBoss source/binary distributions > > > > > > Currently we produce bz2, tar.gz for the sources and bz2, > tar.gz, .zip > > for the binary distros. > > > > There are issues with users using non-gnu tar (for the tar.gz > > distros) that doesn't support long filenames, etc., and at the same > > time, if you look at the download pages only 5-15% will use the > > bz2/tar.gz distros and there are projects (e.g. > > EJB3) that only distribute .zip without problems. > > > > We are thinking of just dumping all extensions except for .zip. > > > > It's what people mostly use, and most installations will have an > > unzip/winzip utility, or a jdk whose bin/jar can unzip the distro > > anyway. It'll make QA's life a little easier, too. > > > > The only dissadvantage AFAIK is .zip doesn't keep the > execution bits > > of files (e.g. .sh) so those have to be set manually after > un-ziping > > (but that's a trivial chmod +x bin/*.sh) > > > > Any views? > > > > jboss-4.0.4RC1-installer.jar 59104072 20249 Platform-Independent > > Other > > jboss-4.0.4RC1-installer.jar.MD5 32 414 > Platform-Independent Other > > jboss-4.0.4RC1-installer.jar.SHA-256 64 174 Platform-Independent > > Other > > jboss-4.0.4RC1-src.tar.bz2 61600096 714 > Platform-Independent Source > > .bz2 > > jboss-4.0.4RC1-src.tar.bz2.MD5 32 62 Platform-Independent Other > > jboss-4.0.4RC1-src.tar.bz2.SHA-256 64 48 > Platform-Independent Other > > jboss-4.0.4RC1-src.tar.gz 65326480 1523 > Platform-Independent Source > > .gz > > jboss-4.0.4RC1-src.tar.gz.MD5 32 64 Platform-Independent Other > > jboss-4.0.4RC1-src.tar.gz.SHA-256 64 38 > Platform-Independent Other > > jboss-4.0.4RC1.tar.bz2 76605812 812 Platform-Independent .bz2 > > jboss-4.0.4RC1.tar.bz2.MD5 32 49 Platform-Independent Other > > jboss-4.0.4RC1.tar.bz2.SHA-256 64 39 Platform-Independent Other > > jboss-4.0.4RC1.tar.gz 81379037 1700 Platform-Independent .gz > > jboss-4.0.4RC1.tar.gz.MD5 32 50 Platform-Independent Other > > jboss-4.0.4RC1.tar.gz.SHA-256 64 33 Platform-Independent Other > > jboss-4.0.4RC1.zip 82323401 13867 Platform-Independent .zip > > jboss-4.0.4RC1.zip.MD5 32 198 Platform-Independent Other > > jboss-4.0.4RC1.zip.SHA-256 > > ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
