X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Andrew Schulman Subject: Re: OCaml package hasn't updated for a while (Ping unison maintainer) Date: Thu, 31 May 2007 11:22:12 -0400 Lines: 19 Message-ID: References: <8363ea9c0705230910l252f2216y1ad42c56d7c21c19 AT mail DOT gmail DOT com> <8363ea9c0705310635y79e08219wc7a121567c955e16 AT mail DOT gmail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive: encrypt X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com > One problem is that a major client of O'Caml is unison, and, because of > binary incompatibility, the releases of O'Caml need to be coordinated with > unison. I've added a ping, and we'll see what Andrew says. I'm not > familiar enough with O'Caml program dependencies to know whether I can > simply provide an older runtime DLL in a separate package or not. There > was some discussion of this earlier -- perhaps I should dig in the > archives. Igor, if you mean that releasing a new OCaml would mean that I'd have to rebuild and rerelease all of the Unison packages, I don't have any objection, assuming the packages will still build without trouble. If the current Unison packages won't run with the new OCaml runtime, then yes, we should coordinate the releases. Once a new OCaml compiler is built I can use it to rebuild Unison. I have to dig back into Unison soon anyway, because a new version is out. A. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/