Michael Goffioul wrote: > 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. > >
How easy would it be to adapt you NSI script to the MinGW package? I also think it would be a good idea to wrap the compilers and the option to install them in the installer as this is where the MinGW installer will excel relative to the MSVC installer. Basically I know nothing above the NSI scripting language and avoided learning it, but it seems that the MSVC and MinGW packages will be so similar that the modifications in NSI for one or the other will be minimal. D. -- David Bateman [EMAIL PROTECTED] 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 ------------------------------------------------------------------------- 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
