Howdy,
the CouchDB project is currently considering writing unit tests which
rely on EUnit, a LGPL library (see
http://svn.process-one.net/contribs/trunk/eunit/doc/overview-summary.html).
As things are never that easy, here are a few more details:
- EUnit itself will not be shipped with CouchDB
- EUnit is actually being bundled with the latest version of the
Erlang runtime/compiler (OTP), which is licensed under the Erlang
Public License, an MPL-derivative (dunno if MPL 1.0 or 1.1). It
doesn't seem like the Erlang team managed to have EUnit relicensed,
though, so whether their bundling is kosher is left as an exercise to
the reader (if it isn't, I'm afraid the violation might still affect
downstream users)
- Execution of tests is entirely optional (compile-time option)
- tests are written using the API of EUnit, in a way that to this
Erlang-untrained eye looks like an import/include clause that makes a
number of functions available (asserting stuff, automatic execution of
all functions ending in _test() - much like JUnit does)
Before the CouchDB community commits to using EUnit for their testing,
some help would be welcome in understanding whether that would be
fine. Suggestions?
--
Gianugo Rabellino
Sourcesense, making sense of Open Source: http://www.sourcesense.com
(blogging at http://www.rabellino.it/blog/)
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org