On Thu, Nov 4, 2010 at 7:40 AM, Adam Kocoloski <kocol...@apache.org> wrote: > On Nov 3, 2010, at 11:53 PM, Noah Slater wrote: > >>> 7. Removing dependencies from the source tree is not going to happen >>> any time soon. I wish we didn't have to vendor so many projects, but >>> we have to remember that a majority of people building CouchDB are not >>> Erlangians. Forcing our community to install a number of Erlang >>> dependencies to build CouchDB would be a very large hurdle to >>> navigate. I know that there are projects like faxien and rebar's git >>> support to overcome this, but I don't feel that there is a solution >>> that sufficiently addresses this issue. >> >> And doing it at build time breaks a really fundamental rule of build systems. >> >> Never assume a network connection > > Can we remove the dependencies from the repository but include them in all > release tarballs? For example, in a rebar world we would call 'get-deps' in > the course of building a release tarball. Throwing away the commit history > of our upstream dependencies makes regression-hunting more difficult than it > needs to be. > > Adam
I'm not entirely against this approach at first glance. Though the thing that comes to mind is how the ASF would view building release artifacts with this much code that's not in SVN. I'll ping infra to see if they have prior experience. Paul
