From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.comp.lib.gnulib.bugs,gmane.emacs.devel Subject: Re: Still unable to build trunk Date: Sun, 23 Jan 2011 20:01:32 -0500 Message-ID: References: <87y66fv2d3.fsf@stupidchicken.com> <4D388F7F.20708@swipnet.se> <87r5c7jk5m.fsf@stupidchicken.com> <4D39EF9C.1050804@cs.ucla.edu> <4D3A8666.4070609@cs.ucla.edu> <877hdvd49f.fsf@meyering.net> <83mxmrzhb6.fsf@gnu.org> <4D3C9C5B.8050303@cs.ucla.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1295830914 5844 80.91.229.12 (24 Jan 2011 01:01:54 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 24 Jan 2011 01:01:54 +0000 (UTC) Cc: bug-gnulib , cyd@stupidchicken.com, Jim Meyering , emacs-devel@gnu.org, Eli Zaretskii , jan.h.d@swipnet.se To: Paul Eggert Original-X-From: bug-gnulib-bounces+gnu-bug-gnulib=m.gmane.org@gnu.org Mon Jan 24 02:01:47 2011 Return-path: Envelope-to: gnu-bug-gnulib@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PhAoU-0002iQ-Q2 for gnu-bug-gnulib@m.gmane.org; Mon, 24 Jan 2011 02:01:46 +0100 Original-Received: from localhost ([127.0.0.1]:50028 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PhAoU-0006m0-60 for gnu-bug-gnulib@m.gmane.org; Sun, 23 Jan 2011 20:01:46 -0500 Original-Received: from [140.186.70.92] (port=34601 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PhAoJ-0006lf-Ql for bug-gnulib@gnu.org; Sun, 23 Jan 2011 20:01:36 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PhAoI-0004qB-WB for bug-gnulib@gnu.org; Sun, 23 Jan 2011 20:01:35 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:52213 helo=ironport2-out.pppoe.ca) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PhAoI-0004q5-Te; Sun, 23 Jan 2011 20:01:34 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAFdePE3O+J3X/2dsb2JhbACkZXS6NIVQBIRwjjqDNQ X-IronPort-AV: E=Sophos;i="4.60,367,1291611600"; d="scan'208";a="89009803" Original-Received: from 206-248-157-215.dsl.teksavvy.com (HELO ceviche.home) ([206.248.157.215]) by ironport2-out.pppoe.ca with ESMTP/TLS/ADH-AES256-SHA; 23 Jan 2011 20:01:32 -0500 Original-Received: by ceviche.home (Postfix, from userid 20848) id 5F31B66102; Sun, 23 Jan 2011 20:01:32 -0500 (EST) In-Reply-To: <4D3C9C5B.8050303@cs.ucla.edu> (Paul Eggert's message of "Sun, 23 Jan 2011 13:23:39 -0800") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-BeenThere: bug-gnulib@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Gnulib discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-gnulib-bounces+gnu-bug-gnulib=m.gmane.org@gnu.org Errors-To: bug-gnulib-bounces+gnu-bug-gnulib=m.gmane.org@gnu.org Xref: news.gmane.org gmane.comp.lib.gnulib.bugs:24877 gmane.emacs.devel:134877 Archived-At: >> It sounds harsh to me to ask every one who builds out of VCS to have >> to climb such a steep curve. > I dunno, I just started doing some Emacs development after > about five years' absence, and it was a pretty steep learning > curve for me. We decided a long time ago that it should be possible to build Emacs from the VCS without autotools. While I don't like having `configure' and other auto-generated files under the control of the VCS, we've learned to live with it and some of those files are related to bootstrap rather than to autotools, so even if we change the decision, we'll still be left with such files. IOW, we still wantfor people to be able to build Emacs from the VCS without needing autotools. If that means keeping aclocal.m4 under the control of Bzr, then so be it. > For example, nowhere is it stated that one really should use the > obsolescent Python version 2.6.6, and that the current Python versions > 2.7.1 and 3.1.3 do not work well with the current bzr version. I had > to find that out myself, the hard way, by making hard-to-diagnose > screwups. That's because noone knows that: the python mode is poorly maintained. Stefan