Re: hosting mingw binaries for octave

[David Bateman]

Benjamin Lindner wrote:
>> Benjamin Lindner wrote:
>>     
>>> Hello list,
>>>
>>> I wanted to grab some feedback on the mingw binary hosting.
>>> Since I personally don't have the webspace to provide bianries, I am 
>>> thinking of creating a sourceforge project. 
>>>       
>> Test binaries I can put up on my personal machine like I did for
>> Michael's MSVC binaries.. However, real releases I'd prefer no to as my
>> upload bandwidth is not unlimited... However, I'd suggest that any full
>> releases are done through octave-forge. We already have MSVC and Mac OSX
>> binaries on octave-forge, so adding a MinGW binary would not be any
>> issue. It might need a little bit of reorganization of the file release
>> system, though that can be rethought out once you have a binary you are
>> happy with.
>>     
>
> Good point. 
> How can I get access to the octave-forge project?
>   
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)...

>>  Check
>>
>> http://octave.cvs.sourceforge.net/octave/octave-forge/admin/Windows/msvc/
>>     
>
> Maybe yes, maybo no. But this should not be a stumbling point.
> Oh, I see that octave-forge uses cvs. Any chance this changes to svn?
> No? Then I definitely need to learn cvs, too ...
>   
A number of time we almost switched to SVN.. We probably still could,
though its always been a lower priority than other things. CVS isn't all
that different in its command set that SVN..

> Hosting all relases on octave-forge can make use of synergies, though.
> For example the source code for dependencies for win32...
>   
Of course ...


>> Useful in 3 years to me means having a maintainer that is likely to stay
>> connected to the distribution :-)
>>     
>
> Touché :). Ja, I see the point, but hey, this is implicitly clear, 
> so I didn't bother mentioning it. 
> The comment was more meant in the way, that if I - for whatsoever 
> reason - am not connected to the binary, it is not too hard for 
> others to see and understand what I did...
> Providing binary releases does only make sense if there is also
> maintainance for them, this is clear.
>   
This is where clear build scripts come in, and perhaps why using the
existing MSVC build script might be a good idea as there would then be
one almost identical build process for the two binaries..

D.


-- 
David Bateman                                address@hidden
Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph) 
Parc Les Algorithmes, Commune de St Aubin    +33 6 72 01 06 33 (Mob) 
91193 Gif-Sur-Yvette FRANCE                  +33 1 69 35 77 01 (Fax) 

The information contained in this communication has been classified as: 

[x] General Business Information 
[ ] Motorola Internal Use Only 
[ ] Motorola Confidential Proprietary