thanks for taking the time to reply
> First, 4.3.1 is a development version. Are you developing against the source to fix a defect or build an enhancement? If not, and you intend to build a version of the server that >you can use in production, I strongly recommend building the latest stable tag from the v4.2 branch, which is currently r4.2.1, rather than building the unstable development >version.
I regularly maintain mongo (from git) on my machines together with a
fairly large number of other packages. In general, I assume that a
tagged commit is "in some way" "testable" and so give it a try (this
is so for almost any other package). I'll change my web checker to
report for stable tags only: thanks for letting me know.
> Regarding the change of the --prefix argument into the PREFIX Variable: we are doing active development work on the build system on the master branch as part of the >upcoming 4.4 release, and the changes you observe are part of that. Those changes are currently incomplete and we have not yet updated the build instructions reflect the work >that has landed. Furthermore, our build and release process doesn't currently use the --prefix argument at all (though the future version will make use of PREFIX), nor do we >document the behavior of that flag in the build documentation.
Actually, I find the following in building.md (r4.3.1)
$ python3 buildscripts/scons.py --prefix=/opt/mongo install
> Could you please provide the complete SCons invocation you are trying to use, and if you intend to continue working on the master branch we can provide an analogous build >command. Otherwise, please switch to the v4.2 branch and you should find that your existing SCons invocation continues to work.
I appreciate your helpfulness: I can go with PREFIX; I was just
curious about the reason why such a common and widespread option as
--prefix had been dropped...
thanks a lot (and apologies for the noise)