For lablgl, I think it's fine to say "glut | freeglut" for the dependency,
but I also notice a problem with O'Caml binaries. If you fink update ocaml
from 3.09 to 3.10, for example, then all O'Caml packages (lablgl included)
will break because of binary incompatibility. For example, they could
disagree over an interface of a standard module. I don't think any O'Caml
package is ready to be put into stable yet. It's just not that stable.

liulk

On Tue, 2 Oct 2007, Alexander K. Hansen wrote:

> Alexander Hansen wrote:
> > On 9/30/07, Chris Dolan <[EMAIL PROTECTED]> wrote:
> >   
> >> On Sep 28, 2007, at 2:04 PM, Alexey Zakhlestin wrote:
> >>
> >>     
> >>> I think, that I read, somewhere, that 2.27 is protocol-compatible with
> >>> 2.13… (though I may be wrong)
> >>>       
> >> The changelog is here:
> >>    http://www.seas.upenn.edu/~bcpierce/unison//download/releases/beta/
> >> unison-2.27.29-manual.html#news
> >> and does not mention anything protocol-related.
> >>
> >> FWIW, I've been using Fink's 2.13.16-1004 daily with many different
> >> configs and have had no problems.  I endorse a move to stable.
> >>
> >> Chris
> >>     
> >
> > I've moved lablgtk and unison to stable.
> >
> >   
> 
> oops, it needed lablgtk2, which itself requires lablgl-x11 (maintainer
> cc'ed).   One issue with the latter package is that it still depends on
> glut, rather than freeglut.  I've tried out an update to that effect,
> which seems OK.
> 
> If there are no objections, I'd like to commit the updated lablgl,
> lablgtk2, and unison to stable this weekend.
> 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to