-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 8/26/2010 12:12 PM, Michael Jackson wrote:
So the boost-svn tracking is now hosted at Github. Ok. If you read farther down the page then it looks like Boost-CMake really _is_ going to be resurrected in the future? Is there any current activity with respect to Boost and git and cmake?
I am so confused. I was going to take over for Troy S. in getting Boost-CMake ready after each release but if there is "Official" work doing this then I am not going to waste me time.
Clarifications would be wonderful at this point.
Let me see if I can clarify. Ryppl is a project started by Dave Abrahams and Troy to simplify and streamline software development, deployment, testing and reporting. It supports Git and CMake natively. Dave A and I are actively working on it. I have also been maintaining a CMake-able and modularized version of Boost (work started by Troy). The guys from Kitware (of CMake fame) want to see this happen too and have been supporting us, making fixes to the CMake files as needed. The vision is that each boost library lives in its own Git repo and states what other libraries it depends on. "boost" then is just another library that depends on a bunch of other libraries. Building and installing Boost is then a matter of making local clones of all the git repos and using cmake to build and install. But ryppl's scope extends beyond boost. There is a project index much like pypi where people can upload and download "packages" (really just links to git repos). Much of this is already working, but we still have a long way to go. What does this all mean for the Boost-CMake fork? Not much in the short term. Ryppl is a long-term project. Even if we achieve our vision, it's not clear that Boost as an organization will adopt it. So don't stop your Boost-CMake work. It works today and meets a real need. Feel free to join the ryppl mailing list or drop by on irc. All that information can be found on ryppl.org. Cheers, - -- Eric Niebler BoostPro Computing http://www.boostpro.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJMdqdaAAoJEAeJsEDfjLbXwkAH/3fYccu7RVjB7kN+RhkzMunl pRp62LnTH3tb2+TwYqksON4cwIDZjBKqh/YhI6kumBulMqZE20HS8PV1w7Z24UV3 +zZPiJz0omXHeSYNxe64i3dixt23LOqa1S4D9sYK/hkwgwXqlWiiR+kOq38u4MV5 VzvivDV8X2keaF63SZqvRvAum6fi1KI9gp+wbhAVOUWXXoctLvPtqAcL51vGFm+S P3UUQ/jA9Xi7bHNazNtnIQmHLrrK1sHHZRzGVSyxOhh4qJW1DYU8RBSWpLBlEDLS 1JKA1mcFCLEcF9MKSY2O7lX70KMyAzMd9DdcmhKpitfZ4MfChheGjGCY0pJSQ5A= =s3L/ -----END PGP SIGNATURE-----