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 576389BCC for ; Mon, 20 May 2013 20:59:50 +0000 (UTC) Received: (qmail 33468 invoked by uid 500); 20 May 2013 20:59:50 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 33427 invoked by uid 500); 20 May 2013 20:59:50 -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 33419 invoked by uid 99); 20 May 2013 20:59:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 May 2013 20:59:50 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,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.128.51 as permitted sender) Received: from [209.85.128.51] (HELO mail-qe0-f51.google.com) (209.85.128.51) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 May 2013 20:59:46 +0000 Received: by mail-qe0-f51.google.com with SMTP id nd7so3203481qeb.10 for ; Mon, 20 May 2013 13:59:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=FhYhXvGLFozzytntN74MfdY48hrYECIsEdMp1ulyIkY=; b=jFLG/f9642tW33SQkHAM2g6Oor4mc4fyHLIrZ44APRNcQWPru8Y2GGr9vTlm9wRqUZ lFj/PLRbG3iLe5Q1qHJDA4DqUmJ0qgSbYW8Co8Kf7R6Ufrlbo7gNhVi2n/9dBbzsahu1 QWfd8Nv9c3C18hQLnSn9eMdmQeBsXxkV9CEv9qPE5xmNJfpYJNdrWipxhchprHXk8OUP UUm9f7592IELo/a2OySazKqfosl8AUhZcxV5ySHuvPqeLFXmm2hgGHCAYIhtut/ntlsH MRKqDGbnPMzgMTlQ1lzR7jogupENYa9ZHH5yp+iRX2k+unBVicasFm0B9kH46USTZna7 gDzg== MIME-Version: 1.0 X-Received: by 10.224.78.11 with SMTP id i11mr2125717qak.29.1369083565297; Mon, 20 May 2013 13:59:25 -0700 (PDT) Received: by 10.49.128.136 with HTTP; Mon, 20 May 2013 13:59:25 -0700 (PDT) Received: by 10.49.128.136 with HTTP; Mon, 20 May 2013 13:59:25 -0700 (PDT) In-Reply-To: References: Date: Mon, 20 May 2013 22:59:25 +0200 Message-ID: Subject: Re: Getting rid of file lists in documentation Makefiles From: Benoit Chesneau To: dev@couchdb.apache.org Content-Type: multipart/alternative; boundary=20cf3074d22a93f2cd04dd2c9be0 X-Virus-Checked: Checked by ClamAV on apache.org --20cf3074d22a93f2cd04dd2c9be0 Content-Type: text/plain; charset=ISO-8859-1 On May 20, 2013 10:56 PM, "Dirkjan Ochtman" wrote: > > On Mon, May 20, 2013 at 5:39 PM, Noah Slater wrote: > > I'm torn on this issue. > > > > See: > > > > http://www.gnu.org/software/automake/manual/automake.html#Wildcards > > > > (Please read that whole section.) > > > > Summary is: > > > > * Wildcards make it easy to distribute the wrong files (either too many, or > > too few) > > > > * Wildcards are not portable > > Yes, I understand the concerns. On the other hand, I don't think most > of those concerns apply cleanly to for example a Sphinx project. In > particular, Sphinx already complains if src files are either missing > or unused, so you'll get warnings about that. And Sphinx populates the > build directory from scratch every time, so problems with the HTML > output also seem fairly unlikely. On the other hand, forgetting to > update the file lists in the Makefile.am will have no effect on > building the docs, but will fail make distcheck. To me, at least, in > this context, DRY a bigger concern to me. > > To be fair, portability is a concern. Dave, does the typical Windows > build environment already have a find tool available to it? (Either > just some compiled GNU tools or a full Cygwin environment?) > > > Please also consider that with Benoit's rcouch merge, we're moving away from > > Autotools entirely (I believe), so we will have the chance to throw off / > > simplify a lot of this stuff. > > Ah, yes. Do we have a time frame for that? sometime this month but before the next. - benoit > > > What are your thoughts having read that section? > > Still the same, in this particular context, for the reasons explained above. > > Cheers, > > Dirkjan --20cf3074d22a93f2cd04dd2c9be0--