Re: [Boost-build] Boost.Build causing failures on the release branch (and Trunk too)

Subject: Re: [Boost-build] Boost.Build causing failures on the release branch (and Trunk too)
From: Vladimir Prus (vladimir_at_[hidden])
Date: 2008-11-19 12:52:06

John Maddock wrote:

> There seem to be a lot of failures on the release branch caused by some
> libraries not being found, so for example on acc:
> 
> http://tinyurl.com/6r76o5
> 
> or on Darwin:
> 
> http://tinyurl.com/6dyezn
> 
> The library not being found is part of the project requirements BTW in case
> that helps,

On the *release* branch? I am confused what is going on -- the only explanation
would be that trunk Boost.Build is being used to test release state of C++ Boost.
Ah, right, I recall we discussed this being the case. So, to summarize,
the current testing arrangement appears to be:

1. For release branch:

        - C++ Boost -- release branch
        - Boost.Jam -- stable release
        - Boost.Build -- bleeding edge

2. For trunk:

        - C++ Boost -- bleeding edge
        - Boost.Jam -- stable release
        - Boost.Build -- bleeding edge

Seem fairly strange to me. For one thing, as I've complained already on
boost-testing, we never test Boost.Jam trunk + Boost.Build trunk, so
we'll never detect any breakage in that combination. And at the same
time, we use in-development version of Boost.Build for release testing.

I would say we should use release branch version of everything for
release branch, and trunk version of everything for trunk.

Speaking of failure itself, I'll have to tweak that code for setting
variables again :-(

- Volodya