Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of dch@jsonified.com designates
 209.85.217.170 as permitted sender)
MIME-Version: 1.0
Date: Thu, 20 Jun 2013 12:12:16 +0200
Message-ID: 
 <CAL+Y1nuBzLN+uZzz1YubLJqSnV7+Vno3Le++ayTiQRumW6WAwg@mail.gmail.com>
Subject: R16B01 + Homebrew, Archlinux etc
From: Dave Cottlehuber <dch@jsonified.com>
To: CouchDB Developers <dev@couchdb.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

Hi folks,

Currently Couch is holding back installation on OS X of things like
Elixir (needs >= R16B) because we don't yet support that.

What's the best way (from our perspective) of sorting this out? Some ideas:

1. a special 1.4.0 release that only support R15B+ is 1.3.1 + the
changes that are only on master at the moment (
1696-update-mochiweb-2-4-2 branch).

2. providing homebrew with a .patch file that sits on top of 1.3.1
release, using a backport approach like macports does
(1696-backport-mochiweb-2-4-2-1.3.x branch).

3. a stable 1.3.1+R16B-backport fork for homebrew with the same fix as
#2.. I would be ok to maintain that until the next master-based
release if required.
(1696-backport-mochiweb-2-4-2-1.3.x branch again). This would be fine
for homebrew team I think.

Would this work for other platforms that tend to use a current Erlang?

Note that the 2.4.2 mochiweb is the *last* release that still supports
< R15B, and it's already at 2.6.0.

Upgrading past v2.4.2 bring us fixes related
 to tcp error handling differences between between R14/15/16:
https://github.com/mochi/mochiweb/commit/56a32a0cc091b69374f35aa0787c36c7776ae816
any opinion on whether this should be included too?

A+
Dave