After all, the toy edition is good enough. It works. It just will come with no guarantees that it won't eat your data, and it will probably be quite slow.
I would be worried about you (in this hypothetical case) being able to reject improvements to the boost version. Boost libraries are not aiming to be "average, good enough" type of libraries, they aim higher. So suppose that someone want to improve the boost versions, because it is all sort of slow bits, would you accept those changes as a library maintainer? Or would you block them because it would ruin your commercial business ?
I've never been in that situation, but what I have in mind has pluggable storage backends with a single frontend API. So if someone wants to develop a competing backend superior to the open source one which directly competes with my commercial one, I'd say rock on. Competition is good! If on the other hand they wanted to extend or modify the frontend API in a way which severely breaks things for my commercial backend, the chances are I'd say no unless it fixes an obvious bug or problem. I would prefer a new breaking version of the library to that, which of course they are free to fork. Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/