John Maddock wrote:
Again: proper component dependency. Depending on trunk version of your dependencies is the root cause of the issue here. One library should depend on specific released version of another library A.deps = B:1.2.3
And again that's not how Boost testing currently works, no matter what you may wish.
The issue here is that breaking changes should not be made to trunk without checking to see what else in Boost is depending on those features. As you know that didn't happen with the last major commit.
One small point: I had this problem many years ago which prompted me to (reluctantly) sever dependency of serialization library from that of Boost.Test. It didn't totally solve my problem because the same issue occurred to some extent with other libraries. It was unavoidable since I was testing the serialization library with other software in the boost trunk - which by definition/custom is experimental. I realized that the real solution was to test the serialization library changes against the rest of boost on the release branch. It permited developers of prerequisite libraries from having to deal with me. Robert Ramey
Regards, John.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost