From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-07-22 09:58:07
> For my project I want to write a document as to what version of BBv2
> to use. I have a few questions:
> - is there going to be a next milestone/snapshot release of BBv2,
> independent of the next release of Boost? It's easier for me
> to say use XXX milestone version or higher, rather than writing a
> document telling people to get the latest stuff from CVS.
In early August I hope.
> - does anyone have experience with packaging BBv2 in something like an RPM?
> I basically want to have an RPM which installs BBv2 in such a way
> that the only thing they need is to have "bjam" in their PATH...
> no other environment variables. I am comfortable with doing
> custom patches to user-config.jam, etc. before creating the final RPM
I did created Debian package for Boost.Build, and it extra simple --
Boost.Build does to /usr/share/boost-build and bjam *already* looks in that
directory. RPM should be no harder, but I no longer have RPM system around,
so can't test.
One question is whether site-config.jam or user-config.jam should contains
'using gcc ; ' already, or expect the users to add it. I'd be inclided to say
we need "using gcc ; ".
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