Re; A MinGW release tomorrow?

[David Bateman]

For the 100MB file size, Seb can we work on stripping it down in size 
before it goes on octave-forge. There are lots of development files, 
that don't need to be there that ca be removed. The gnuwin32 stuff will 
be easy to strip for this, though the code built from source a bit 
harder. For example all of the hdf5 binary utilities are in this package 
and probably don't need to be, and lots of other things like that. Also 
there is still a small problem in the octave build where it tries to 
link copies of some things, that might get a gain in size. I'm sure we 
can probably halve the size of the file in an eventual release.

I'd also like to have ATLAS and NSIS working before migrating it to 
octave-forge, as having a proper setup.exe will be essential prior to a 
real release. If you release something that is even slightly hard to 
install, you are asking for an enormous workload of support questions. 
Asking a user to set an environment variable and edit a file if they 
don't install in c:\octave is a great way of getting numerous such 
questions.

Seb, if you goal is really to host a development binary, as I did for 
you rather than a real release, then I can place it on my home server.

Quentin, although I have the ginac/gmp/cln libraries installed, the 
symbolic toolbox is the only octave-forge toolbox I couldn't yet get to 
build correctly. It is the only missing octave-forge toolbox at this point..

Cheers
David