From: Vladimir Prus (ghost_at_[hidden])
Date: 2002-05-14 09:55:12
David Abrahams wrote:
> > For one thing, it's not fancy but rather dumb :-)
> > I'm not sure. The new startup behavour really simplify things but I'd
> > still like to be able to use Boost.Build without any setup.
> What kind of setup do you think is needed at this point?
You should specify the location of build system by either BOOST_BUILD_PATH
var or using boost-build.jam file.
> > > I don't think we need to save the links to Boost.Build as a separate
> > > but if we do, someone needs to make a file for the target of the link!
> > I suggest that we dump this as well. I've updated the page on the trunk,
> > not on the RC_1_28_0 branch. I'll try to do a merge right now.
> Make sure you've tagged the trunk revision as specified in the release
> process page to prevent further merge problems.
As *not* specified in the release process page -- merging from trunk to
release branch is omitted :-)
I've tagged the release branch with RC_1_28_0_last_merge, so if anybody will
try to merge index.html back to trunk, he won't get conflicts.
> > > Note that the older versions of the Boost.Jam rpms are no longer up
> > > so old versions of the Boost CVS will contain broken links.
> > Is is a problem? Links to the Jam RPMs will be broken as well, because
> > package names include the version number.
> That's exactly what I was saying.
> I don't know if it's a problem. I'm inclined not to break the existing
> Boost website, and to let people with 1.27.0 download from their local
Well, I can try to put the RPMS back....
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