Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of adam@cloudant.com designates
 209.85.216.180 as permitted sender)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1251.1)
Subject: Re: multiple repo &
From: Adam Kocoloski <adam@cloudant.com>
In-Reply-To: 
 <CAJNb-9qRqv9mPN78SYsRL=5Gfk3-+n1erdTZ=yhbsUK-QN2W4g@mail.gmail.com>
Date: Sat, 7 Jan 2012 10:37:32 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <F003307A-8BDB-49FD-8A48-21F4346F59EE@apache.org>
References: 
 <CAJNb-9qRqv9mPN78SYsRL=5Gfk3-+n1erdTZ=yhbsUK-QN2W4g@mail.gmail.com>
To: dev@couchdb.apache.org

Thanks for bringing this up.  Regardless of whether we eventually store =
our own applications in individual git repositories I think the ability =
to pull in external repos will prove useful in tracking upstream changes =
from third party applications like mochiweb and ibrowse.  The current =
approach of copy/pasting source code is error-prone and has caused some =
breakage in the past.

I certainly understand the importance of the build system being =
self-contained, but I think the source release described by Benoit =
covers that.

Adam

On Jan 7, 2012, at 9:25 AM, Benoit Chesneau wrote:

> Hi all,
>=20
> I would like to start some work on my own to test how I can merge our
> autotool build system and rebar to provide an erlang release and
> distribute couchdb more easily. In refuge I consider that all the apps
> in src/ are standalone app and each have their own history (old
> couchdb history is kept) .  To create a release, the make distdir
> collect all the deps and in one source dir and the archive is created
> from that source directory. At the end the created release is the same
> you have with couchdb and you don't need to have git installed to
> build it. Packages created (deb, rpm & osx) are based on this source
> release.
>=20
> Can we do the same in the apache project ? Ie having one git repo /
> app ? Or do we still need to handle them in the same repo ? Just
> wanted to ask to know how I should handle that or at least start the
> integration of rebar.
>=20
> Let me know,
>=20
> - beno=EEt