John Maddock writes:

I've made a set of summaries for BSL conformance available at http://freespace.virgin.net/boost.regex/index.html

There's one summary per library + one for all of Boost, I'd encourage everyone to take a look to see whether their work can be used under the BSL alone, or if there are non-BSL dependencies that they rely upon.

Reports starting from "tuple" and down the list appear to be missing. -- Aleksey Gurtovoy MetaCommunications Engineering

John Maddock writes:

I've made a set of summaries for BSL conformance available at http://freespace.virgin.net/boost.regex/index.html

There's one summary per library + one for all of Boost, I'd encourage everyone to take a look to see whether their work can be used under the BSL alone, or if there are non-BSL dependencies that they rely upon.

First of all, thank you for your work on this! Question: is there a reason why we cannot automatically convert all these "Boost Software License, Version 1.0 (variant #N)" to the canonical wording? -- Aleksey Gurtovoy MetaCommunications Engineering

"John Maddock" <john@johnmaddock.co.uk> writes:

I've made a set of summaries for BSL conformance available at http://freespace.virgin.net/boost.regex/index.html

There's one summary per library + one for all of Boost, I'd encourage everyone to take a look to see whether their work can be used under the BSL alone, or if there are non-BSL dependencies that they rely upon.

Note that there are one or two cases where dependencies are found that are not real: filesystem for example ends up being shown as dependent upon the Graph lib (not under the BSL), but this is an illusion, based on iterator_adapters pulling in some python headers, which leads to a presumed dependence upon the python source.

I just checked in some fixes for that dependency. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com