From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.devel Subject: Re: Checkout of Emacs CVS through firewall Date: Thu, 10 Jun 2004 10:03:42 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <20040610095444.CABC.JMBARRANQUERO@wke.es> References: <20040609173532.1C7F.JMBARRANQUERO@wke.es> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1086854662 27839 80.91.224.253 (10 Jun 2004 08:04:22 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 10 Jun 2004 08:04:22 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Thu Jun 10 10:04:14 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BYKXl-0001hk-00 for ; Thu, 10 Jun 2004 10:04:13 +0200 Original-Received: from lists.gnu.org ([199.232.76.165]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BYKXl-0007wF-00 for ; Thu, 10 Jun 2004 10:04:13 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BYKYR-0003T3-Mt for emacs-devel@quimby.gnus.org; Thu, 10 Jun 2004 04:04:55 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BYKYN-0003Sx-WA for emacs-devel@gnu.org; Thu, 10 Jun 2004 04:04:52 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BYKYJ-0003Sj-1t for emacs-devel@gnu.org; Thu, 10 Jun 2004 04:04:51 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BYKYI-0003Sg-Uv for emacs-devel@gnu.org; Thu, 10 Jun 2004 04:04:47 -0400 Original-Received: from [62.22.181.117] (helo=idefix.laley.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BYKXH-0008Rf-PI; Thu, 10 Jun 2004 04:03:44 -0400 Original-Received: from [172.17.221.23] (JMBARRANQUERO [172.17.221.23]) by idefix.laley.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55) id LSNJ69FJ; Thu, 10 Jun 2004 10:02:59 +0200 Original-To: Miles Bader In-Reply-To: X-Mailer: Becky! ver. 2.08.01 [en] X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:24793 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:24793 On Thu, 10 Jun 2004 10:33:57 +0900 Miles Bader wrote: > There are pretty likely to be some problems if you build-in-place, as I > never do that (and apparently other arch users are the same). Well, I've opted now to have a build directory, rsync'ed from the copy I update from your system. I don't mind the disk space and I think I'll probably avoid a lot of trouble. > Looking at your list, all the duplicate ids starting with "i_" are due > to that; I'll see what I can do to fix those (part of the problem is > that autoconf doesn't have a useful "strip this comment in the generated > file" syntax). Yeah, nt/configure.bat has no way to do that either. I'd be necessary to require yet another tool, like sed or perl, and That's Not Good. > The rest of the problems (unknown directories "bin", "data", "lock", > "site-lisp"; directory "etc/icons" apparently a copy of "nt/icons") seem > to suggest you're also _installing_ into the source tree. That's just > brain-dead, don't do that (does the windows makefile advocate this?!?) No, it doesn't advocate it, and neither does forbid it. I know some projects (like GCC) advise against building in place, but I've never heard such a thing wrt Emacs, and in fact I do it all the time with no ill effects. "cvs update" just shows there are a few "unknown" (i.e., "?") directories and files, and that's all. > -- there's only so much that can be done if you insist on crapping all > over the source tree. It seems wise to work *with* the tool and not *against* it, so from now on I won't do inplace builds on Arch-controled copies :) Thanks, Juanma