unison formal review

Kevin Fenzi kevin at scrye.com
Wed Sep 28 21:15:58 UTC 2011

On Wed, 28 Sep 2011 22:00:40 +0100
"Richard W.M. Jones" <rjones at redhat.com> wrote:

> I checked the source code, and unison sends a header which contains
> the current major version number of the software (where "major
> version" is a string, currently "2.40").  If the major versions of
> each end don't exactly match, unison aborts.  It would be possible,
> albeit complicated, to combine all versions of unison together somehow
> and switch on the major version.

I think you can run it with a switch or compile time option to make it
pass the full version so you could have unison-2.40 and unison-99 on
the remote end and it would start the right one. 

> I was thinking of something slightly simpler: a single 'unison'
> package that contained several binaries, like /usr/bin/unison227,
> /usr/bin/unison (symlink to latest).

That does help with needing re-reviews and names and such, but it
doesn't help in that you have to update everything everytime a new
version comes out. 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
Url : http://lists.fedoraproject.org/pipermail/devel/attachments/20110928/be99d01b/attachment.bin 

More information about the devel mailing list