From: Nicola Musatti (Nicola.Musatti_at_[hidden])
Date: 2006-05-07 17:16:55
Russell Hind wrote:
> It could be done again as a separate project (in fact, we import each
> boost release in to our own svn repository at work and modify it and
> version internally ourselves).
> But I'd rather see it done as a complete source tree, rather than a
> patch as bcbboost is. i.e. if we are to do this, then import the
> current boost-1.32.0 in to a new svn repo at sourceforge and then modify
I agree about your inhouse repository - I have one too - but I'm not
sure I'd like to maintain a repository the size of Boost on SourceForge
just for the sake of a few tens of files worth of patches.
> But if there aren't many people requiring this, then perhaps it is
> overkill. If I get the chance to look at getting 1.32.0 working with
> BDS 2006 internally then that is a start. Once that is done, I can
> think about how to make it more public.
Consider using bcbboost! It would be a pity to scatter Boost BCB support
> Integrating spirit as the default would be a good move too (again, that
> is what our svn repo of boost contains).
I have to say that at one time I thought we were closer to issuing a BCB
compatible Spirit 1.6.4 version, otherwise I would probably have
uploaded my own version to the bcbboost site. Still, the current
SPIRIT_1_6 branch in the Boost repository is BCB compatible.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk