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: Change to bzr build instructions Date: Tue, 22 Mar 2011 03:16:18 -0400 Message-ID: <7paagnaam5.fsf@fencepost.gnu.org> References: <30r5a1s4kt.fsf@fencepost.gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1300778197 8786 80.91.229.12 (22 Mar 2011 07:16:37 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 22 Mar 2011 07:16:37 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Mar 22 08:16:32 2011 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 1Q1vpQ-0004de-HU for ged-emacs-devel@m.gmane.org; Tue, 22 Mar 2011 08:16:32 +0100 Original-Received: from localhost ([127.0.0.1]:59540 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q1vpP-000558-CM for ged-emacs-devel@m.gmane.org; Tue, 22 Mar 2011 03:16:31 -0400 Original-Received: from [140.186.70.92] (port=39095 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q1vpF-00054Q-M3 for emacs-devel@gnu.org; Tue, 22 Mar 2011 03:16:22 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q1vpD-0004nL-Ss for emacs-devel@gnu.org; Tue, 22 Mar 2011 03:16:20 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]:49402) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q1vpD-0004nH-Q2 for emacs-devel@gnu.org; Tue, 22 Mar 2011 03:16:19 -0400 Original-Received: from localhost ([127.0.0.1]:49887) by fencepost.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q1vpC-0002LR-Gg; Tue, 22 Mar 2011 03:16:18 -0400 X-Spook: BRLO diwn militia IMF FTS2000 22nd SAS Ft. Knox Arnett X-Ran: uT~SN@]lN"+AT5uZ=P}x4l}7;)B\Q-V5v0hCCljm 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:137514 Archived-At: >>> So we should either be more careful about such dependencies in >>> copy_autogen, or maybe try and get copy_autogen to set >>> "enable-maintainer-mode=off". >> I suppose it could do something like that, but I don't know if it is a >> good idea. I really don't recommend the use of the copy_autogen script >> at all, except very much as a last resort, so I wouldn't want to see it >> get too fancy. > > I don't think we want to get too fancy, indeed. The `touch' trick seems > sufficient for now. To elaborate, if the autogen/configure script is one with maintainer-mode = off by default, then if someone uses it, they won't get any prompting to update configure if configure.in changes in the repository. At least with the current situation, they will get an error about missing autotools, which will hopefully prompt them to run copy_autogen again. On this subject, what to do about maintainer-mode in releases? At present, I put a note in admin/make-tarball.txt saying that the configure in a release tarfile should be generated with maintainer-mode off. i) It's rather poor to have to remember to change that. ii) Is it actually necessary to make such a distinction? If configure.in etc are not changed, it does not matter, and if someone does edit configure.in, arguably they _should_ get an updated configure. This seems to be what automake recommends now: http://www.gnu.org/s/hello/manual/automake/maintainer_002dmode.html (or is it actually recommending removing the option altogether, and having it always on?)