Re: hosting mingw binaries for octave

[John W. Eaton]

On 27-Aug-2007, David Bateman wrote:

| Asking here is a good start.. We need your sourceforge username though
| as I don't believe you are registered as an octave-forge developer..
| You'd also need to be marked as a release technician in octave-forge to
| be able to upload files. However, we'd need to think about how to
| reorganize the release page to handle up to three different and
| concurrent Windows releases (MSVC, cygwin and MinGW)...

Given that Cgywin has its own packaging and distribution system,
perhaps the Cygwin binary should be dropped from the Octave Forge
site?  Doesn't it just cause trouble to have a Cygwin binary that is
separate from the Cygwin package system?  I think that is especially
true if the separate binary is not even compiled with the normal
Cygwin compiler.  I think it would be much better to work with the
Cygwin people and find a way to fix the GCC problems on Cygwin
systems.  If that can't be done, then maybe it's time to give up on
Cygwin (at least as far as Octave is concerned).  I don't see why that
would be a problem if we have a native Windows binary that works
better anyway.

jwe