From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2008-06-26 19:17:15
Jurko Gospodnetic' wrote:
> Hi Rene.
>> Please refrain from messing with this in the trunk until after the
>> 1.36 release. We already have a problem with someone changing test
>> tools code. And we can't afford to have a halt in testing at this time.
> Hmmm... shouldn't Boost library testing use a release or at least a
> separate branch of Boost Build instead of locking down development on
> the trunk?
The BBv2 releases have never been consistent enough to rely on following
that for testing use, unfortunately. But regardless, the release
procedures point out that every attempt should be made to keep trunk in
stable and working order. Previous understanding has been that we would
avoid last minute changes to BBv2 for releases. The key point is that
this particular change looks high risk since it tries to fix something
that is currently working on the platforms it's intended to work on.
I.e. the msvc.jam commands where never intended, and never will be
intended, to work in any shell other than the CMD.EXE shell.
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk