Right now we're providing the official, released, stable version. That's what we should provide.
-Kevin Ballard On Feb 17, 2008, at 9:08 AM, Paul Guyot wrote: > I'd say the good strategy is to have the ubiquitous version. At some > point I synchronized the version of unison with the version > available with FreeBSD ports because it's what I used on the other > end. On the other hand, debian/stable is lagging so much that they > probably should not be considered as a reference. > > Paul > > Le 17 févr. 08 à 14:36, Kevin Ballard a écrit : > >> No, the solution here is to not do anything. Anybody using 2.13 needs >> to upgrade if they want to work with 2.27. We are not in the business >> of providing old port versions, and we *should not* be. >> >> If you're using debian/stable, just install unison 2.27 yourself. >> IIRC >> the default location is $HOME/bin, so you don't need to do *any* work >> to install it besides download the source and build it. Presumably >> you >> have ocaml installed already. >> >> -Kevin Ballard >> >> On Feb 16, 2008, at 8:18 PM, Vincent Lefevre wrote: >> >>> The unison port has recently been upgraded from 2.13 to 2.27. The >>> problem is that the protocol has changed between these versions, >>> and unison 2.13 can't talk to unison 2.27: >>> >>> http://trac.macosforge.org/projects/macports/ticket/14172 >>> >>> The only solution that can work in every case (because users may >>> need >>> to do synchronization with machines that only have 2.13 and machines >>> that only have 2.27) is to install the two binaries: unison-2.13 and >>> unison-2.27 (note: when executing the remote unison binary, unison >>> can >>> automatically add its main version number thanks to the addversionno >>> option). So, I think that the best solution is to have a port for >>> the >>> old version unison 2.13 (BTW, this is what Debian does for the 2.9 >>> version and will probably do for the 2.13 version), which installs >>> only >>> the unison-2.13 binary (alternatively, there could be a variant that >>> installs a "unison" binary too for those who don't need unison >>> 2.27). >>> In this case, what should the name of the port be? unison-2.13? >>> unison2.13? >>> >>> -- >>> Vincent Lefèvre <[EMAIL PROTECTED]> - Web: <http://www.vinc17.org/> >>> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/ >>> blog/> >>> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS- >>> Lyon) >>> _______________________________________________ >>> macports-dev mailing list >>> [email protected] >>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev >> >> -- >> Kevin Ballard >> http://kevin.sb.org >> [EMAIL PROTECTED] >> http://www.tildesoft.com >> >> >> _______________________________________________ >> macports-dev mailing list >> [email protected] >> http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev > > -- > http://paul-guyot.com/ > > > -- Kevin Ballard http://kevin.sb.org [EMAIL PROTECTED] http://www.tildesoft.com _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
