From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Glenn Morris Newsgroups: gmane.emacs.devel Subject: Re: configure{.in,} question Date: Mon, 25 Oct 2010 14:37:48 -0400 Message-ID: References: <09k4l72w3b.fsf@fencepost.gnu.org> <83r5fe6te5.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1288031889 4139 80.91.229.12 (25 Oct 2010 18:38:09 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 25 Oct 2010 18:38:09 +0000 (UTC) Cc: julien@danjou.info, Stefan Monnier , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Oct 25 20:38:07 2010 Return-path: Envelope-to: ged-emacs-devel@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 1PARvq-0003Uu-T9 for ged-emacs-devel@m.gmane.org; Mon, 25 Oct 2010 20:38:07 +0200 Original-Received: from localhost ([127.0.0.1]:57801 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PARvq-0000ee-4J for ged-emacs-devel@m.gmane.org; Mon, 25 Oct 2010 14:38:06 -0400 Original-Received: from [140.186.70.92] (port=33314 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PARva-0000cU-Ou for emacs-devel@gnu.org; Mon, 25 Oct 2010 14:37:51 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PARvZ-0002iP-Kp for emacs-devel@gnu.org; Mon, 25 Oct 2010 14:37:50 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]:55468) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PARvZ-0002iJ-JL for emacs-devel@gnu.org; Mon, 25 Oct 2010 14:37:49 -0400 Original-Received: from rgm by fencepost.gnu.org with local (Exim 4.69) (envelope-from ) id 1PARvY-0007bR-4K; Mon, 25 Oct 2010 14:37:48 -0400 X-Spook: Operation Iraqi Freedom Maple AVN investigation Sears X-Ran: &3D/LrB91x+Ll]K&>L&HwX9B}u0x#v,}5,'jn:5Rv=k%m=wCfF$mUzc|wcQSc:,h.`A&V` X-Hue: white X-Attribution: GM In-Reply-To: <83r5fe6te5.fsf@gnu.org> (Eli Zaretskii's message of "Mon\, 25 Oct 2010 20\:04\:34 +0200") User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:132102 Archived-At: Eli Zaretskii wrote: >> I often end up with problems because of configure and >> src/config.in. > > Including with bzr? What problems are those? If you run autoconf locally (which I think is good practice), and you did not use the same version as the person who last committed configure, you WILL get a conflict when you update. Eg http://debbugs.gnu.org/cgi/bugreport.cgi?bug=6428 http://debbugs.gnu.org/cgi/bugreport.cgi?bug=6536 I update and build my local copy of Emacs with a script, and I run `bzr revert --no-backup configure src/config.in' before `bzr pull/up' (and later `autoconf') to avoid this problem. > a feature on the Bazaar list. If you get lucky, you could have a POC > plugin in a matter of days. But we cannot make everyone who checks out Emacs from bzr use said plugin.