Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 70EC77CAD for ; Thu, 3 Nov 2011 16:08:37 +0000 (UTC) Received: (qmail 7608 invoked by uid 500); 3 Nov 2011 16:08:36 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 7573 invoked by uid 500); 3 Nov 2011 16:08:36 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 7554 invoked by uid 99); 3 Nov 2011 16:08:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Nov 2011 16:08:36 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of bchesneau@gmail.com designates 209.85.215.180 as permitted sender) Received: from [209.85.215.180] (HELO mail-ey0-f180.google.com) (209.85.215.180) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Nov 2011 16:08:31 +0000 Received: by eyg5 with SMTP id 5so1618998eyg.11 for ; Thu, 03 Nov 2011 09:08:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=jEku4nIYP72foroTUF+RNQzYGTU6uMLh2ip/CxL6D1o=; b=hmmAP2392JuWifOwB746S6dIXAU4DKZvpuKbaIsocSaXqFLpnpQ/kmOwJ70p+ApFJz rYuCYSOTif4AZYjY+cmx8HvdO94W/xWPW1ovOIZ5ejI9PEWBSUj4GiaJMC0SXSk3yxGw GN0YeIsmD6/ACeg1wRkju9aXoqW3gJ3Iz1X6U= MIME-Version: 1.0 Received: by 10.14.22.197 with SMTP id t45mr474458eet.94.1320336490397; Thu, 03 Nov 2011 09:08:10 -0700 (PDT) Received: by 10.14.37.193 with HTTP; Thu, 3 Nov 2011 09:08:10 -0700 (PDT) In-Reply-To: <785FABDB-2EF0-409A-A6C5-E9C8D498241B@apache.org> References: <785FABDB-2EF0-409A-A6C5-E9C8D498241B@apache.org> Date: Thu, 3 Nov 2011 17:08:10 +0100 Message-ID: Subject: Re: Binary Downloads From: Benoit Chesneau To: dev@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Thu, Nov 3, 2011 at 12:35 PM, Jan Lehnardt wrote: > Hi all, > > I think we should start considering providing binary downloads for our us= ers. > > The whole topic is a bit of a mess (see below), so I'd propose to start s= mall. > > 1. This first iteration are links from couchdb.apache.org that are clearl= y > =A0 marked as "unofficial 3rd party binary downloads" that are not hosted= on > =A0 ASF infrastructure. > > 2. Start with popular platforms. > > 3. Use the build-couchdb* script to create a fully self-contained directo= ry with > =A0 CouchDB and all its dependencies in one place that can be rm -rf'd fo= r > =A0 uninstalling. > > * https://github.com/iriscouch/build-couchdb > > > The above circumvents several things that I hope we can resolve later, bu= t that > I don't consider blocking us from getting the above started. > > A. Official ASF releases. Of course, ideally, we should provide official = ASF > =A0 binary releases, but I acknowledge that with a small community, we ma= y have > =A0 trouble getting votes and testing for all popular platforms together. > > =A0 The nice thing of the proposal above though is, that we can, at any t= ime > =A0 promote an unofficial build to an official one by voting on it and ch= anging > =A0 it's label on the downloads page. > > B. There's many target platforms our users work with and we can't possibl= y try > =A0 to service them all at once. We can grow this operation as we get vol= unteers > =A0 to help out with each platform. > > =A0 The nice thing here is that we can help a significant portion of user= s with > =A0 relatively little effort. > > C. Using existing package managers. There are many advantages to use offi= cial > =A0 package managers for system installation and they should in fact be t= he > =A0 preferred way to set up a system, but they tend to be a little bit be= hind > =A0 with current releases. > > =A0 I'd be super happy to also work with existing package managers to imp= rove > =A0 the situation there, but I consider this to be outside of the scope o= f this > =A0 discussion. > > > What do you think? > > Cheers > Jan > -- > > Ah, quite interresting topic. Thanks to raise it! I'm +1 on the idea to have "official binaries" but I really dislike the idea to have to use build-couchdb for that. Or any system that use rakes, ruby, python .... where we could just use erlang and unix tools. It does the job but it's petty ugly (Jason, no offense, build-couchdb does its job quite well). I think to do the right job we could: - adapt the build system to build proper elang release (using reltools). We can wrap rebar for that since it's pretty efficient these days and well supported (allows parralel builds, release buils and clean updates) but this isn't really required, it can be perfectly handled by autotools. (I think that using rebar would give us more options though). The advantage of using erlang release tools is that we can cleanly manage the modules we need. You can manage templates, so other distributors can adapt it to their system. - Create a toolchain =E0 la mozilla that would allows later to introduce later cross-complication and start to support other platforms. They are petty good for that and I think we can borrow a couple of ideas. I would be really interested to work on such things. Also maybe with a proper toolchain we could setup a build-bot that create nightly releases and such. - benoit