Am 5.11.2010 18:57, schrieb Thomas Friedrichsmeier: > On Friday 05 November 2010, Patrick Spendrin wrote: >> Well, making a restriction in the installer is the first task. The >> sources for the installer are in trunk/kdesupport/kdewin-installer - it >> is normal Qt application ;-) > Alright, I'll take that as a go-ahead and start looking into it. Are you aware that adding an additional executable with mostly the same functionality may result into more problems than to solve ?
There is a concept that the last recent installer is always named kdewin-installer-latest.exe. The url of this installer is spread all around the world, has been linked into many websites and is downloaded up to 100000 times a month. When this option is removed from the installer and for each compiler a different url is provided, who is going to talk with all those website maintainers to add additionals link in case more than one compiler is supported. Or if only one compiler is supported, who will explain users 10 times a day, why compiler xyz isn't available anymore. Having all this possibilities in one installer makes it able to change installers behavior from release to release without any broken links and increased support requests by this. In the opposite there is the single installer approach with a minimal gui approach, see http://www.winkde.org/pub/kde/ports/win32/setup/stable/ - but in both case some people are not satisfied. Ralf _______________________________________________ Kde-windows mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-windows
