unison: warn about OCaml version incompatibilities

2014-10-16 Thread Christopher Zimmermann
Hi, I keep being asked why unison fails to work since the upgrade to OCaml 4.02. Therefore I'd like to add this piece of information to the install message. The patch is just for my convenience when debugging. Is it ok to commit this patch, too? Unison comes in stable and snapshot versions. The

Re: unison: warn about OCaml version incompatibilities

2014-10-16 Thread Giovanni Bechis
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/16/14 13:38, Christopher Zimmermann wrote: Hi, I keep being asked why unison fails to work since the upgrade to OCaml 4.02. Therefore I'd like to add this piece of information to the install message. what about putting the MESSAGE in a

Re: unison: warn about OCaml version incompatibilities

2014-10-16 Thread David Coppa
On Thu, Oct 16, 2014 at 2:30 PM, Giovanni Bechis giova...@paclan.it wrote: I am not using unison,-snapshot, it is unhooked since a lot, I think it can be removed. +1 Ciao! David -- If you try a few times and give up, you'll never get there. But if you keep at it... There's a lot of problems

Re: unison: warn about OCaml version incompatibilities

2014-10-16 Thread Stuart Henderson
On 2014/10/16 14:32, David Coppa wrote: On Thu, Oct 16, 2014 at 2:30 PM, Giovanni Bechis giova...@paclan.it wrote: I am not using unison,-snapshot, it is unhooked since a lot, I think it can be removed. +1 Probably makes sense to move net/unison/stable/* to net/unison/* as well (this

Re: unison: warn about OCaml version incompatibilities

2014-10-16 Thread Stuart Henderson
On 2014/10/16 13:38, Christopher Zimmermann wrote: Hi, I keep being asked why unison fails to work since the upgrade to OCaml 4.02. Therefore I'd like to add this piece of information to the install message. Ugh! In a previous version, they had this ... Update to 2.40.102 fixes an

Re: unison: warn about OCaml version incompatibilities

2014-10-16 Thread David Coppa
On Thu, Oct 16, 2014 at 2:40 PM, Stuart Henderson st...@openbsd.org wrote: On 2014/10/16 14:32, David Coppa wrote: On Thu, Oct 16, 2014 at 2:30 PM, Giovanni Bechis giova...@paclan.it wrote: I am not using unison,-snapshot, it is unhooked since a lot, I think it can be removed. +1

Re: unison: warn about OCaml version incompatibilities

2014-10-16 Thread Christopher Zimmermann
On Thu, 16 Oct 2014 14:41:37 +0200 David Coppa dco...@gmail.com wrote: On Thu, Oct 16, 2014 at 2:40 PM, Stuart Henderson st...@openbsd.org wrote: On 2014/10/16 14:32, David Coppa wrote: On Thu, Oct 16, 2014 at 2:30 PM, Giovanni Bechis giova...@paclan.it wrote: I am not using

Re: unison: warn about OCaml version incompatibilities

2014-10-16 Thread Christopher Zimmermann
On Thu, 16 Oct 2014 13:41:43 +0100 Stuart Henderson st...@openbsd.org wrote: On 2014/10/16 13:38, Christopher Zimmermann wrote: Hi, I keep being asked why unison fails to work since the upgrade to OCaml 4.02. Therefore I'd like to add this piece of information to the install message.

Re: unison: warn about OCaml version incompatibilities

2014-10-16 Thread Stuart Henderson
On 2014/10/16 15:15, Christopher Zimmermann wrote: On Thu, 16 Oct 2014 13:41:43 +0100 Stuart Henderson st...@openbsd.org wrote: On 2014/10/16 13:38, Christopher Zimmermann wrote: Hi, I keep being asked why unison fails to work since the upgrade to OCaml 4.02. Therefore I'd like

Re: unison: warn about OCaml version incompatibilities

2014-10-16 Thread Stuart Henderson
On 2014/10/16 15:08, Christopher Zimmermann wrote: Thanks for the hints! So is the following diff OK? yep. Someone told me CVS will clean up the empty directories on its own, doesn't it? It cleans them at checkout/update time as long as you use -p, there's no real way (short of messing with

Re: unison: warn about OCaml version incompatibilities

2014-10-16 Thread Giovanni Bechis
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/16/14 15:08, Christopher Zimmermann wrote: Thanks for the hints! So is the following diff OK? ok giovanni@ Someone told me CVS will clean up the empty directories on its own, doesn't it? sthen@ has been exhaustive. Cheers Giovanni