On 9/23/05, Michael Schumacher <[EMAIL PROTECTED]> wrote:
> michael chang wrote:
> > Solution: Linux/POSIX emulation layer.  Cygwin is usually used.
> > MinGW/MSYS is also workable, IIRC.  I've never compiled GIMP on either, 
> > though.
> For GIMP, I'd say that MinGW is preferred - not that there shouldn't any

I prefer MinGW myself, but I believe that if the guy knows how to
compile on Linux, it might be more familliar to him to emulate
Linux/POSIX on Windows with Cygwin than figure out MSYS/MinGW.  But
then again, I found it easier to get used to MSYS/MinGW than Cygwin,
so... *shrugs*

> > Of course, at the end of the day, I think it'd be nicest if they made
> > an installer for the Windows binaries for the development releases,
> > but I'm quite sure that's probably more work than it's worth.
> Problem: how to keep each of the places distributing GIMP (some net
> magazines, other random websites, users) from mistaking it as a new
> stable release.

How about not releasing it on the standard page (e.g. "hiding" it in
the developer website somewhere)?

I like the timeout idea too, personally -- POV-Ray (www.povray.org)
has monthly timeouts for its various beta versions (and they have a
new "beta RC" every month).  The problem is that when the timeout
dies, then should be a new version; if there isn't one, it's kinda
silly to have to re-install the same version to extend the timeout. 
In that case, determining a timeout would be hard...

 - Just my two cents
 - No man is an island, and no man is unable.
Gimp-developer mailing list

Reply via email to