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 paul.joseph.davis@gmail.com
 designates 74.125.83.180 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=DbPMnjxoSkp5GDXp6zNqLNRdb4DJcfJ3rYQf+Iy3ZUkBKpjasJBbMClyiUnAZYOJ1Y
         ZfUPIkdyXfUObZygkeoUZbujVmpvBwONG/95MN+cVMvzMczeQ4XwUnq1iQXfaeXCPY1u
         MlAOiGJjyENJ7yiQix3Itw3mDQRYjiNCc3rfw=
MIME-Version: 1.0
In-Reply-To: <AANLkTik-e+v7jcTYT7+k0A1F2+kJiXD_HE87d-fB1=Os@mail.gmail.com>
References: <AANLkTimNk_96tNkZC57WYMg-u8=1Aa30J6dpZSN0RsMv@mail.gmail.com>
 <AANLkTim8kqN9knN5Y7_5Q3pCEJ8D44yQykHF6GWb+nv1@mail.gmail.com>
 <F796ABEF-828F-428C-B67E-25A4B40D7621@apache.org>
 <AANLkTikZsv=-4FJird+-s6xLx6Et+P_nFKW=rW6yTx7e@mail.gmail.com>
 <791E5E22-088B-424C-83BF-506FECA8D9F3@apache.org>
 <AANLkTimhpY2HXtAoPtRwRzHsaVfQkYzG70Yt3QbKefJ_@mail.gmail.com>
 <AANLkTimRdTUV0YyM4FpUwfv+Zh3PbevSncZnj2-rNwMJ@mail.gmail.com>
 <5653D2A8-0656-4D1B-87D7-D6185E6E2015@apache.org>
 <9634B73E-6F1D-4B4F-8F38-997C24C28C2A@echolibre.com>
 <AANLkTik-e+v7jcTYT7+k0A1F2+kJiXD_HE87d-fB1=Os@mail.gmail.com>
From: Paul Davis <paul.joseph.davis@gmail.com>
Date: Thu, 4 Nov 2010 11:26:43 -0400
Message-ID: <AANLkTimEs4=Mf4NG05KVM1=D3d=rdzaqvfY4e6gB2JAn@mail.gmail.com>
Subject: Re: CouchDB OTP
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Nov 4, 2010 at 11:07 AM, Tristan Sloughter
<tristan.sloughter@gmail.com> wrote:
> This is a great discussion and I want it to keep going. But I'm going to try
> to lay out how I plan to move forward and hopefully this will help in the
> future.
>
> I'm going to use autotools for building only the C pieces and not for
> anything else. I want to be able to use this as a normal release/target
> system afterwards installed like any other. So I don't want to use something
> for placing config files or whatever. I know that won't mold well with the
> normal CouchDB use-case but maybe its simple to do both... Or I'll realize
> thats futile and do something with setting where configs live through
> sys.config when its passed to erlexec...
>

I haven't yet spent much time contemplating how these bits are going
to interact. I'll be very interested to see how you approach things
here to make things work with Rebar and Sinan.

> Anyway, I'd hope my fork could be seen as a testbed of sorts. As I said, it
> should be buildable with rebar as well.
>

Having an example on how the code looks using Sinan or Rebar will be
an awesome start as I begin digging into how some of the unexciting
parts of the build. I'll be watching your repo as you hack there and
if you don't mind I plan on using you as a sounding board while I
puzzle through these different parts.

Paul Davis