Testing and reports are very welcome !
I will continue our PM conversation here since files can not be attached to PM, and all this would probably interest some other fpcup users...
Everything works again with latest fpcup. Tested in Win7 32bit VM. Lazpaint module does not hang the whole process any more and is properly built. SVN client download url is correct now and SvnURL modules work again even on a machine without any SVN client preinstalled. GitURL and HgURL work when proper clients are preinstalled (tested with TortoiseGit and TortoiseHg). GitURL will not work if during GIT for Windows installation default "Use Git from Git Bash only" is selected. Selecting "Use Git from the Windows Command Prompt" worked for me. This is info that does not exist in any fpcup documentation I could read so it should probably end up in a wiki page.
Mormot is default module in fpcup. I think it should not be default. Just let the user use it if he wants. That way if it goes wrong, fpcup with default settings will still be able to finish it's job.
Bgra now compiles without manually commenting the problematic line (trunk seams to be corrected), but anchordocking seams to have a problem in laz trunk (I think, since it works with laz 1.4). It compiles well but has a serious layout save/restore bug which completely kills usability. It is not a fpcup problem but it is worth mentioning for current users.
Again, attached BAT file
TrunkAll downloads trunk fpc and trunk laz, while
TrunkLaz BAT file downloads stable fpc (2.6.fixes) and trunk laz (with all modules). There is nothing windows specific in BAT files so they should be cross compatible. Of course, attached
FPCUP.INI and
MYSETTINGS.INI should be put into FPCUP.EXE directory. I have modified them and corrected errors where needed, so using them now allows downloading correctly all modules (anchordocking, bgracontrols, brookframework, codelibrarian, dcpcrypt, default, doceditor, ecc, fblib, fpcdocs, fpcup, fpspreadsheet, glscene, greyhound, helpfpc, helplazarus, indy, kzdesktop, lazarus_ccr, lazbuild, lazdatadesktop, lazpackager, lazpaint, lazres, leptonica, lhelp, ljgridutils, lnet, mormot, mupdf, nxpascal, OCRivist, pascalsane, patchwrangler, rx, simplegraph, suggestedpackages, synapsetrunk, tesseract, tiopf, USERIDE, vampyre, vtv and zeos). I have not yet tested installerlazwin module.
I have extended lazarus_ccr module so now it downloads complete repo and installs these additional components: cmdbox, lazcolorpalette, fpspreadsheet, fpspreadsheet_visual, fpspreadsheetexport_visual, gradcontrols, jujiboutils, JvCoreLaz, JvNavigationPaneLaz, JvXPBarLaz, kcontrolslaz, lazbarcodes, longtimerpackage, tponguard, playwavepackage, poweredby, pack_powerpdf, richmemopackage, lazrichview, scrolltext, spktoolbarpackage, tdi, lazparadox, tvplanit, virtualtreeview_package, and zvdatetimectrls. Other packages are listed but commented for various reasons. More info about it can be read inside FPCUP.INI. I have corrected GitURL paths for these modules: brook, tiopf, lazpackager, ljgridutils, greyhound, lazmupdf, fblib and mormot. It works now for me, so check if it works for you. I have also corrected modules 18, 19, 22, 39, 40 and 41. Please take a look and apply if you agree with such changes. With tiopf we need to execute "git checkout tiopf2" from tiopf source dir. You will see my unsuccessful attempt to automate this in FPCUP.INI, so please take a look and see if you have a better idea which would work. So far it needs to be done manually.
My further steps would be to try to add new modules I proposed earlier (again time is the limit), and after that I would try to
add CodeTyphon exclusive modules to fpcup. It would not be needed to download the whole 600MB CT archive since I have already found while monitoring CT updater with WireShark that just interesting files can be downloaded from these locations:
http://www.pilotlogic.com/codetyphon/current/src/typhon_src.7z (35MB with all CT components)
http://www.pilotlogic.com/codetyphon/current/src/CodeOcean.7z (optional 125MB with all CT examples)
Then I would have to find a way to unpack them (7zip is still not supported in fpcup), programmatically change pl_* required package references in code as I already do by hand, and install them. Everything automated. I would also make a special module called max that would include all other modules, and user should be able to easily install or update Lazarus with zillion components, libraries and frameworks with just a single fpcup command.
As a general idea, it would be good if we could parameterize module to be installable only on specific operating system and bitness. Something like AllowedOS=win32,lin32,lin64 or similar in FPCUP.INI definition of that module. Does something like that already exist?