On Tue, Aug 3, 2010 at 12:53 PM, Greg Troxel <[email protected]> wrote: > >>> http://tahoe-lafs.org/source/tahoe-lafs/snapshots/tahoe-lafs-ticket798-1.8.0β.tar.bz2 … >> http://tahoe-lafs.org/source/tahoe-lafs/snapshots/tahoe-lafs-ticket798-1.8.0%ce%b2.tar.bz2 … > Well, the link works, but then when firefox saves it I get a file with a > ? in it.
Okay, how about this: http://tahoe-lafs.org/source/tahoe-lafs/releases/tahoe-lafs-ticket798-1.8.0b.tar.bz2 > Part of the motivation for just using b is that packaging systems (not > that this should really be packaged) need to be able to compare versions > for what's higher. The open source world really needs a standard for > how to use version numbers, but the two de facto schemes are the old FSF > 1.7.1.80 scheme and saying 1.8.0b1 for the first beta. I've never seen > anyone use non-ascii characters and have no reason to think any of the > comparison functions in various package managers will get this right. Hey that's a good point. Now for what it is worth, the "tahoe-lafs-ticket798-1.8.0β.tar.bz2", or the identical "tahoe-lafs-ticket798-1.8.0b.tar.bz2" contains software which, if you execute "./bin/tahoe --version" will print out: "tahoe-lafs-ticket798: 1.7.1-r4653". The final release of Tahoe-LAFS v1.8.0 when it comes out (probably around August 15) will print out "tahoe-lafs: 1.8.0". Regards, Zooko _______________________________________________ tahoe-dev mailing list [email protected] http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
