Benjamin Lindner wrote:
>
> I hope this is the correct place to ask, I loked around the project and
> it seemed the most appropriate list.
>
> I'd like to (finally) contribute binary packages of octave built with
> and bundled with the mingw32 gcc.
>
Great, I added the release technician flag to your account so you can upload
the binaries, the only question is where and what. I'd also suggest you look
at the "releaseforge" project that is a much better means to upload than
what sourceforge provides.
> I had a look at the download section and found that there are are
> already some package sections.
> Now the questions is how to add the mingw32 binaries into the download
> structure of the project.
>
The structure will have to be revised. At the moment there is a "Octave
Forge WIndows" section and a section for additional packages. Michael has
started including all packages in the NSI installer and so the additional
packages subsection should go away. I'd therefore suggest having and "Octave
Forge Windows - MSVC" and "Octave Forge Windows - MinGW" section on the
download page.
> What I'd like to provide is:
> 1) Octave mingw32 binaries
> 2) the corresponding Sources & Patches (Octave and all dependencies
> included) - compliance to GPL etc.
> 3) ATLAS v3.8.1 binaries for some architectures
>
> 1) and 2) should be fairly obvious, I guess.
>
Supply the source tarball is easy enough, though huge. As for the binaries
and atlas libraries, frankly I'd prefer that the whole lot was wrapped up in
an NSI installer like Michael's package and the appropriate library
installed as needed.
> Item 3) should be a seperate item IMO, since these binaries do not
> follow the release cycle of octave, and therefore are kind of a general
> add-on to many octave binaries. I therefore would distribute them
> seperately from the octave binaries.
>
> I would suggest therefore 3 new sections, like
> "octave forge windows mingw32 binaries"
> "octave forge windows mingw32 sources"
> "octave forge windows mingw32 atlas"
>
If the atlas is in the installer then it makes sense to keep the binary and
source packages together in the same sub-sub section of the download page.
Or one could combine the atlas binaries into the binaries section be
relinking them to every new release (supposing this is possible)?
Like having the sections
"octave forge windows mingw32 binaries"
"octave forge windows mingw32 sources"
and the binaries containing, e.g.
<Octave n.n.n for Windows/mingw32>
<Octave n.n.n for Windows/mingw32 - ATLAS>
i.e. two new entries for every new version/release of octave.
Or adding the ATLAS binaries to every released binary directly. Like
"OCTAVE FORGE WINDOWS MINGW32"
<Octave n.n.n for WIndows/mingw32> - 2008-mm-dd
- a-binary-file-of-octave
- a-different-file-maybe-installer-or-other-zip-format-binary
- ATLAS-binary-ARCH_1
- ATLAS-binary-ARCH_2
- ATLAS-binary-ARCH_3
...
Comments?
NSI and a bit of help from Michael :-) In any case I'm not sure you need
all of those ATLAS libraries. I'd probably only keep SSE2 and perhaps SSE3
libraries as most machines support that and use generic blas for the rest.
Aside from the structure definitions:
who can add/modify the download page structure?
who can then actually add files to the download section?
me? an admin only?
You can now that i've added the flag :-)
D.
--
View this message in context:
http://www.nabble.com/Uploading-mingw32-octave-binaries---where-and-how--tp18141114p18141922.html
Sent from the octave-dev mailing list archive at Nabble.com.
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Octave-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/octave-dev
