Re: More: Compatibility issues

> In the Migration Guide, you speak about Client Versions and Server
> Versions, but if I understand correctly there is only one unison
> program which can be installed on the "Server" (the machine initiating
> the sync) or the "Client" (the machine being remotely called for the
> sync)?

There is only one program.  client and server are roles for a particular
sync.

> If I get 2.52 or 2.53 installed on the server, do I understand that it
> will be backward compatible with 2.51 or 2.48 installed on the client
> machine, irrespective of the OCaml version of the client unison,
> PROVIDED that I regenerate the archives files (your wording is hazy
> since it says only that "same OCaml version" is needed for
> interoperability).

Before 2.52, data structures and wire protocols changed formats when
ocaml versions changed (usually).

Now, data structures are independent of ocaml versions.

So if you upgrade to 2.53.3 -- or better 2.53.4RC1 -- then you will have
to regen archive files.  One should always, before any upgrade, get
everything in sync.

As for interop with 2.48 and 2.51, you will need a 2.53.x with an
adequately matching ocaml version.

Overall, my take is that 2.48 especially and 2.51 are too old to deal
with and should be upgraded.  Complaints that packaging systems still
have them should be directed to those packaging systems.

Go to

  https://urldefense.com/v3/__https://github.com/bcpierce00/unison/actions/runs/7902642581__;!!IBzWLUs!QEIVM-_uGakJs5vOnMyyyiW1f5dKGENS_pjBkEZkKFb6Fq9Q_Z49t7fEyspO2btgqNICflKxDGIwPFzd8Q$ 

and scroll down.  You'll see artifacts named by OS and ocaml version.


Whether ubuntu 22.04 is compatible with 20.04, it's very likely, because
if not I bet somebody would have said so.  I don't know if ubuntu
publishes binary compatibility rules, and if so, if they follow them.
But it looks like our builds now use 22.04 mostly.


As for installation, these are tarballs (well they are zip) that contain
binaries.  You'll have to deal with it manually.   Yes, uninstall the
package first.



-- 
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].