Volodya wrote:
> On Wednesday 26 April 2006 21:50, Alex Besogonov wrote:
>
> > Maybe we can setup a Wiki to draft the
requirements for the BBv3?
>
> Hi Alex,
> I'm a bit nervous about "BBv3". You see,
what we have now is not ideal, but
> it's working codebase. I seriously doubt that there
are architectural changes
> that can't be done on the existing code (or its Python
port), and given large
> number of tests, after the changes Boost.Build will
continue to be usable. So
> I think the best course of action in the mid-time would
be:
>
> - Finish C++ Boost transition to V2
Wholeheartedly agreed.
> - Port V2 to Python
I agree.
> - Gradually change architecture to any new
requirements
Agreed.
I think it would still be a good idea to set up a Wiki
(BB/Evolution?) that would
allow us to document:
* what we want/require from the Python port:
* do we use the SCons dependency system, rewrite the BB
one or use
something else?
* get rid of the jamfile hacks (i.e. replace set.jam
with Set)
* what features/properties do we want in a future version
of BB? (see my
ramblings in my previous post  )
- Reece
____________________________________________________________
_____
Express yourself instantly with MSN Messenger! Download
today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471
ave/direct/01/
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
|