Deploy and install both require some special dependencies that aren't always available for every developer. Most developers also aren't interested in building those repositories. For this reason, these dependencies are considered optional in configure, only causing warnings to be printed if missing and just disables the building of that repo. For RE, this is inconvenient. The build goes on for a long time and doesn't fail when a dependency is missing or wrongly configured. Instead things are just missing at the end.

To help fix this situation, I would like to add two new options to configure: --enable-deploy and --enable-install. When each of these is added, it changes a missing dependency into an error and fails configure. When not added, the build should behave as it does now.

This could be taken one step further by adding another option, with something like --enable-re-build, that would enable the default set of stricter parameters, like those above, with one single option. This could help RE not having to keep track of which platforms actually support what and keep that knowledge in the build scripts. In the future, this option could also include stricter version checking compilers.