I wrote that FCS is a close sourced project, not a commercial product. I also didn't said that involved projects would depend on FCS.
We know Graeme is a huge fan of Git, but as far as I know Git doesn't really fit the purpose.
I haven't looked at mseGUI yet but I'm surprised that Graeme tries to mock what I consider a flaw of fpgui. The "--assureconfigurationfile" parameter is just an idea, here comes the history behind it.
1. I've tried to install the latest stable fpgui but I couldn't because fpgui's building script had a "-dRELEASE" parameter or something like that. The presence of this parameter made the script useless, unable to build fpgui on my system. Hmmmmmm...
2. I've removed the parameter and then I've realized that the script is not able to build fpgui using neither a specific fpc compiler executable, neither using a custom saved fpc.cfg. I reffer to the path of these two files. OOO boy...
3. After that, I've noticed that the build script doesn't build fpgui's IDE(Maximus) neither the UIDesigner. This means that the building process requires running different scripts located in different directories. OOO mama...
4. Knowing that Paul Breneman has experience with fpgui I've said OK, I will completely ignore fpgui's building scripts and write new ones within the flavour file, but there was an additional problem. fpgui's IDE doesn't have a setting(macro) for setting the fpc configuration file. This means that even if FCS would build fpgui using a fpc compiler and fpc.cfg files located in a directory that doesn't belong to the PATH environment then the IDE would be useless. Maximus would be useless because it has to build projects using custom located fpc installation and it doesn't have an entry for the fpc's default config file path. Curses...
5. If you don't install fpc in default locations the configuration is important. Building the IDE and immediately storing involved variables is great in this situation. I think it would be great if installing scripts would fill the values by default but they don't. Imagine building the IDE with a fpc(including its config file) located in /home/xxxx/yyyy/NOTINPATH/fpcinstalldir. When the user opens the IDE he has to fill lots of empty values. Lazarus is one step ahead, it uses some default values and tries to verify them, Maximus doesn't do that. Also, if FCS would try to fill those values it can't do that because it doesn't know where the configuration file is stored and if it has usable content. I'm losing temper here...
6. Obviously, after the above nightmare, I'm still unable to build a project using fpgui's IDE.
So, here was my proposal to all of you main developers. Can we do something to improve the experience of building/configuring/installing the fpc and the IDEs, or not!? You can improve that without FCS or myself. Do you think I would be glad to write scripts within the flavour for an IDE that I don't use!? It's just that, for different reasons, people wait for others to do something and I don't want to share this attitude. I don't believe in licenses either, reason why we have this discussion here.