couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Samuel Newson <>
Subject Re: third-party products and git submodules
Date Wed, 08 Jan 2014 10:21:20 GMT

I think the source code has to be present in our repository directly (and then only if the
licenses are compatible, which seems to be the case for the two you mention). Given that git
submodules are pretty nasty to work with and the subtree merge that is the recommended alternative
will include the code directly, the path forward seems clear.

For example, I imported rebar into the bigcouch merge branch using 'git read-tree --prefix=src/rebar/
-u rebar' where the 'rebar' branch was a verbatim upstream rebar branch.


On 8 Jan 2014, at 08:39, Benoit Chesneau <> wrote:

> Hi all,
> I was reading the "Third-Party Licensing Policy" document [1] from the
> Apache foundation, and it's not totally clear if I can or can't link a
> third-party product as a git submodules.
> My goal was to add spidermonkey (MPL1.1) and ICU (MIT llike) as submodules
> to the rcouch branch to allow static binding of them in a couchdb release.
> On release the modules could be fetched and shipped with the archive. Some
> major products are doing such things around (v8 for ex with ICU). I am not
> sure it's possible with spidermonkey.
> submodules are a possibility. I was previously fetching these third-party
> products during the build. Maybe it can be done differently.
> Any idea is welcome,
> - benoit
> [1]

View raw message