From: Andrey Melnikov (melnikov_at_[hidden])
Date: 2005-09-16 18:45:39
Reece Dunn wrote:
> Example: I am keeping Boost in perforce as part of my "thirdparty" area.
> This allows me to create a branch of BBv2 to another area that I can
> develop new features, making it easier to keep up-to-date with BBv2
> changes. I currently have a cvs2perforce script. It would be nice to do
> something like:
> d:/thirdparty> bjam update dir=boost
> Example: The Boost regression testsuite is checking out the latest CVS
> to run the tests on. You could have an update target in the main
> Jamfile[.v2] that allows you to get the latest (or a specific version)
> of Boost. e.g.:
> d:/thirdparty/boost> bjam update-cvs # get latest version
> d:/thirdparty/boost> bjam update-cvs label=1_30 # get Boost 1.30
> This would probably end up overwriting your Jamfile/BBv2, though :(!
> However, you can have BBv2 separate from Boost :).
> There are also common operations like comparing files/directories and
> checking files in that it is easy to get wrong, especially if you are
> not familiar with the command-line of a specific VCS. Having it in the
> build system allows you to do:
> ...> echo Bugfixes for foo > desc.txt
> ...> bjam checkin-cvs branch=RC_1_34 desc=desc.txt
> ...> bjam diff-cvs # diff files with latest version
> ...> bjam diff compare-with=...
> I am not sure how these will work with BBv2, but this is the sort of
> thing I am referring to.
Do you mean you want a unified command line interface to version control
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