"2 Getting the dependencies" also gets obsoleted by no longer supporting the "default" build: qt4/py2. It seems obtuse to me to have a project where the default build is known not to work and is dependent on package versions which have been declared "obsolete" by the devs, and for which there is no intention to support or even test current master for such builds. No one seems motivated to correct that which seems strange.
Since some time in August when changes to add coolant control to the UI were merged, PathWB simply fails to load. This also destroys any toolcontrollers the user had without any prior warning. Not nice.
The dev who works on that stated clearly that he has no wish to even test it against py2 builds nor to render it compatible. So this is not a question of anyone testing on a particular distro. It is fact. Master still builds on py2 but the result fails to load PathWB and destroys the user's tool config. IMO this should be trapped at compile time, not just dump on the user.
python2 support officially goes at the end of the year and FreeCAD is ahead of the game.
I agree about build scripts. There are so many moving goal posts with the number of deps FC has that it may be wiser not to even provide them. General tips and caveats and package lists for each distro would be helpful but if you are going build something like this out of tree, you really need to be ready to roll your sleeves up, not just cut and paste.
If I get granted the honour of wiki edit rights , I will try to bring the Fedora tips up to date.