On 09.10.2017 19:15, Edward Diener via Boost wrote:
On 10/9/2017 7:09 PM, Robert Ramey via Boost wrote:
On 10/9/17 3:20 PM, Tom Kent via Boost wrote:
On Mon, Oct 9, 2017 at 10:45 AM, Peter Dimov via Boost < Can we back out this change until we can figure out a way to do it where it doesn't break our regression suite?
I don't believe there is a way to specify that the master tests use the master version of build, If I recall, a long time ago, we decided to use a separate version of build for the regression tests, instead of the one tied from the superproject? Is this just the head of develop? Does anyone remember the rationale for this?
Cant we just use the master version of boost build for ALL the testing - master and develop branch? Does it make sense to use an experimental version of the test tools to test anything?
Am I the only one who thinks it logical that a regression test for 'master' should use the 'master' branch of everything and the regression test for 'develop' should use the 'develop' branch of everything ? Why is this even going to be debated ? I have no idea why the 'master' branch uses the 'devlop' branch of Boost Build, but that does not seem like it can ever be right.
Indeed. Though, I agree with Robert and would go one step further: Given that the things under development are the boost libraries, not the tools used to build and test them, I would prefer to use a stable Boost.Build release, even when building and testing Boost's "develop" branch. Stefan -- ...ich hab' noch einen Koffer in Berlin...