Benjamin Lindner wrote:
>
> OK, I took a look at it, and installed the win32 version.
> But it does not really seem to work - The program just hangs after
> entering sourceforge username&password. ??
>
Ok I don't see this issue luckily as an octave-forge release would be
painful without releaseforge. Though as I don't use Windows I don't know how
it works under windows to help here
> So what's the preferred way to do it via sourceforge's interface?
>
> How's that working anyway? - I mean the principle of releases on
> sourceforge.
>
Sourceforge calls this interface the "File Release System" or FRS. When you
log on to the sourceforge website at
https://sourceforge.net/account/login.php
it brings you to you personal page. If you then go to octave-forge's project
page at
https://sourceforge.net/projects/octave
you'll now have an "admin" pull-down menu as you're flagged as a
release-technician, with the "file release" menu item. From there you're in
the heart of the file release system for octave-forge and you can add files
or new sub-projects. Keep everything flagged hidden till the upload is right
however to avoid mistakes. The page
http://alexandria.wiki.sourceforge.net/File+Release+System+-+Offering+Files+for+Download
was information on the FRS.
>> I'd therefore suggest having and "Octave
>> Forge Windows - MSVC" and "Octave Forge Windows - MinGW" section on the
>> download page.
>
> I agree. Who should add the new section?
>
We need to consider relative to the existing Windows sub-projects
* Octave Forge Windows
* Octave Forge Windows - Additional Packages
Ideally as Michael included all of octave-forge in his installer, I'd
suggest hiding the "Additional Packages" sub-project, renaming the existing
project, and adding a new one for MinGW like
* Octave Forge MSVC Windows
* Octave Forge MinGW Windows
However, then it would be better if the MinGW installer also included the
octave-forge packages.
> OK, I had a look at michael's .nsi installer script and took the basic
> structure and some features from it and added the octave binaries along
> with msys+mingw32-gcc+gnuplot+editor and the ATLAS libs into a single
> installer.
> This and the same packed in a simple archive along with atlas libs
> should satisfy both the I-favor-an-installer-users and the
> no-frills-just-unpack-it-users.
>
I know of no WIndows users who prefer simple archives for complex installs
like Octave. I'd suggest not supplying one as it'll just cause confusion.
>> 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.
>
> Yes, I have now generic, SSE, SSE2 and SSE3 libs. This should do it.
>
I don't imagine there are too many SSE machines still running Octave out
there, so if it makes life easier or the binary smaller why not drop the SSE
atlas.
Cheers
David
--
View this message in context:
http://www.nabble.com/Uploading-mingw32-octave-binaries---where-and-how--tp18141114p18306423.html
Sent from the octave-dev mailing list archive at Nabble.com.
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Octave-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/octave-dev
