On Thu, Jun 26, 2008 at 9:49 PM, dbateman <[EMAIL PROTECTED]> wrote: > 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.
My opinion is that you should put yourself in the place of a Joe user that wants to install your package. It's not user-friendly at all to tell him "you need to download package A; if you want feature B, you'll also need to download package C and D; depending on your CPU (see page E to find out your CPU architecture), you can also download packages F1, F2 or F3, but package F1 is also compatible with architecture F3; Oh, and by the way, you can also use the package G, which is the same as package A, but includes F1". OK, I'm exaggerating a little bit, but you get the point. A normal user doesn't want to deal with that. That's why I'm playing with installers, even with simple add-ons. Michael. ------------------------------------------------------------------------- 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
