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 A03F47199 for ; Fri, 4 Nov 2011 01:22:16 +0000 (UTC) Received: (qmail 53711 invoked by uid 500); 4 Nov 2011 01:22:16 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 53675 invoked by uid 500); 4 Nov 2011 01:22:16 -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 53667 invoked by uid 99); 4 Nov 2011 01:22:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Nov 2011 01:22:16 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.210.180] (HELO mail-iy0-f180.google.com) (209.85.210.180) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Nov 2011 01:22:09 +0000 Received: by iaeh11 with SMTP id h11so3024384iae.11 for ; Thu, 03 Nov 2011 18:21:49 -0700 (PDT) Received: by 10.42.202.17 with SMTP id fc17mr12063004icb.15.1320369709271; Thu, 03 Nov 2011 18:21:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.142.43.18 with HTTP; Thu, 3 Nov 2011 18:21:28 -0700 (PDT) In-Reply-To: References: <785FABDB-2EF0-409A-A6C5-E9C8D498241B@apache.org> From: Jason Smith Date: Fri, 4 Nov 2011 08:21:28 +0700 Message-ID: Subject: Re: Binary Downloads To: dev@couchdb.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Love it. FWIW, here are some thoughts from Build CouchDB feedback. On Fri, Nov 4, 2011 at 5:26 AM, Jan Lehnardt wrote: > Randall, Till, > > I had hoped I addressed this in my original mail, but let me try again :) > > I'm in favour of all the things your are saying, but I'm trying to addres= s this scenario: > > $ wget $url > $ tar xzf $archive > $ ./$dir/couchdb > =C2=A0Time to relax. Basically, I suggest clearly identifying every non-goal early. It will help to assess exactly what people want. I am not sure ./bin/couchdb is what people want. I've seen disappointment from build-couchdb users. The world has changed since Noah ported CouchDB to autotools. System administrators are an endangered species. Time was, once you got `make install` working, it was downhill from there. Now, people don't find that as relaxing. * If there is a system couch, you get a long scary message with 'eaddrinuse' buried somewhere in it * When you reboot or computer crashes (possibly 6 months later), Couch isn't running anymore * Log rotation doesn't work (eventually breaking the /_log query in version =3D< 1.1.1) * It's unclear how a backup/restore would work. * It's unclear how an upgrade would work. * It's only "native" in the strictest sense, you can't manage it with the OS (i.e. it's not an .app bundle, .msi installer, .pkg, .rpm etc.) The first email I got about Build CouchDB, somebody said thanks and that it helped. Not one hour later, two emails complained that there is no Ubuntu package. It was really discouraging. But I'd done poor expectation management. So, the above may be excessive for now, but at least clearly describe goals and non-goals. --=20 Iris Couch