On 16 Feb 2009, at 11:36, Antony Blakey wrote:
On 16/02/2009, at 8:58 PM, Damien Katz wrote:
I'm wondering would any downstream project need to ship a fully
assembled CouchDB project, with all its dependencies including the
test suite?. I can't think of a reason, but if there was one it
could cause problems.
Yes - my desktop client, which I anticipate being O/S at some stage.
What's your exact problem? I understand you have a all-in-one solution
including Erlang/OTP and everything else you need to run your
application.
That means you're bundling OTP and I don't think you plan to relicense
it?
Bundling OTP after R12B-5 means, at the moment, shipping LGPL code
in form of EUnit. The LGPL is non viral and you do not (have to)
relicense
EUnit itself. All of your code can be whatever license you plan to use.
Whether we use EUnit or not is not part of this equation. If it were,
do you
need to run the unit-test suite (that is used to ensure no module API
breakage) as part of your application? The functional HTTP API test
suite will be written in JavaScript and stay Apache 2.0 licensed.
I'd love to see your project coming to fruit (and O/S), I sure hope this
is not a deal-breaker for you. If it is, we should consider switching to
etap.
Cheers
Jan
--
