On Thu, Aug 25, 2005 at 01:31:19PM -0400, Christopher Faylor wrote: >On Thu, Aug 25, 2005 at 01:04:25PM -0400, [EMAIL PROTECTED] wrote: >>The Unison developers have released new stable and beta releases of >>Unison. As Karl M pointed out, the compatibility restrictions between >>versions have been relaxed beginning with version 2.13: two versions of >>Unison are now compatible iff the first two numbers in their version >>string are the same, e.g. all versions 2.13.* are mutually compatible. >>So, the new packages are named unison2.13 and unison2.17. >> >>I have also updated the descriptions of the available Unison packages in >>each of the unison2.9.1, unison2.9.20, unison2.10.2, and unison2.12.0 >>packages, and prepared new point releases of each to include that >>change. >> >>Please review the new unison2.13 and unison2.17 packages, and if they're >>suitable, upload them and also the new releases of the other Unison >>packages. > >I'm uploading these now. > >Just a heads up to avoid duplication.
These are all uploaded. FWIW, I used this wget command to grab the files: wget -np -nH --cut-dirs=3 -r -g on http://home.comcast.net/~andrex/cygwin/... Unfortunately, I couldn't use a wildcard to download since comcast seemed to block that. So, I had to download each file one at at time. It was still nice to have the directory structure maintained, however. I downloaded these to a separate directory then used 'cp -a -l . ~release/unison' to copy them over. Then I deleted the original directory. This makes the update more atomic than doing a normal copy or downloading the files directly to the release directory. I deleted older versions of packages where appropriate. FYI. cgf P.S. Thanks, Andrew for making sense out of this version number insanity.
