Paul Baxter wrote: [snip]
I'm slightly surprised that boost build V1 is 'disappearing' because I also see it as a boost library, something that users have been using for larger projects. Can you point me to where it stated in previous releases or on the website that v1 wouldn't be available for this release. Perhaps a period of 'deprecated' but available might be in order.
I'm not disagreeing that from a maintenance point of view, boost itself should all build with v2 and be the way forward, just that removing v1 support in Robert's script rather than keeping a v1 copy in a deprecated area may be problematic to people who have large developments built on v1. I'm not even suggesting V1 need be actively supported as an alternative in v1.34 of boost, just that it isn't actively removed.
FWIW, I agree. Keeping BBv1 in CVS and instead making BBv2 the default when executing "bjam" for this release would be easier on the users, in combination with adding support for "bjam --v1". Perhaps also some deprecation warnings should be output when building with v1. BBv1 could then be removed from Boost CVS in 1.35 and made available as a separate download (tgz, zip). / Johan