From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: David Caldwell Newsgroups: gmane.emacs.devel Subject: Re: Mac OS X GNU Emacs Installer (make-package) Date: Sat, 30 Nov 2002 19:38:08 -0800 Sender: emacs-devel-admin@gnu.org Message-ID: <2147483647.1038685088@[10.0.0.2]> References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1038713920 4812 80.91.224.249 (1 Dec 2002 03:38:40 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 1 Dec 2002 03:38:40 +0000 (UTC) Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 18IKwJ-0001FT-00 for ; Sun, 01 Dec 2002 04:38:39 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 18IL4e-0002FQ-00 for ; Sun, 01 Dec 2002 04:47:16 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10) id 18IKvi-0001L5-00; Sat, 30 Nov 2002 22:38:02 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10) id 18IKvL-0000zL-00 for emacs-devel@gnu.org; Sat, 30 Nov 2002 22:37:39 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10) id 18IKvJ-0000yy-00 for emacs-devel@gnu.org; Sat, 30 Nov 2002 22:37:39 -0500 Original-Received: from [65.211.227.66] (helo=control2.indigita.com) by monty-python.gnu.org with esmtp (Exim 4.10) id 18IKvJ-0000yt-00 for emacs-devel@gnu.org; Sat, 30 Nov 2002 22:37:37 -0500 Original-Received: from [10.0.0.2] (sc-24-30-184-132.socal.rr.com [24.30.184.132]) (authenticated (0 bits)) by control2.indigita.com (8.11.0/8.11.0/Debian 8.11.0-6) with ESMTP id gB13bU102171 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (192 bits) verified NO) for ; Sat, 30 Nov 2002 19:37:33 -0800 Original-To: emacs-devel@gnu.org In-Reply-To: X-Mailer: Mulberry/3.0.0 (Mac OS X) Content-Disposition: inline Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.devel:9775 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:9775 On 11/30/02 5:53 PM -0800 Steven Tamm wrote: > Yeah, I think you are right. The one concern that I had was what would > happen if the location of the Emacs.app was moved. Your solution fixes > that by creating a "shadow" application. Why not make the whole > Emacs.app directory be a link to the lib-exec one? That way you wouldn't > have the problem of dealing with two sets of files depending on whether > you did it from the command line or from the finder. The downside is > that the icon in the Applications menu would be a little screwed up. I really wanted to do cp -lr but OS X cp doesn't support -l. In the end I did this: [david@Bluey ~/src/emacs-dev/emacs-cvs/mac]$ find /Applications/Emacs.app -type f | xargs du -s 8 /Applications/Emacs.app/Contents/.cvsignore 8 /Applications/Emacs.app/Contents/Info.plist 14168 /Applications/Emacs.app/Contents/MacOS/Emacs 8 /Applications/Emacs.app/Contents/PkgInfo 104 /Applications/Emacs.app/Contents/Resources/Emacs.icns 16 /Applications/Emacs.app/Contents/Resources/Emacs.rsrc 8 /Applications/Emacs.app/Contents/Resources/English.lproj/InfoPlist.strings And decided that it was negligible to have a complete copy in libexec (as long as Contents/MacOS/Emacs was a link...). > As another aside, I think the make-package script should eventually be > rewritten in perl because of the guarantee that it exists on Mac OS X. > Any objections. I'm a big perl fan so you won't hear objections from me :). > If Emacs.app is a symlink then it's a non-issue (obviously). pax at that > point is just a wrapper around tar (see the man page), so I would assume > it would do the right thing in any case. Symlinking the whole app works just as well. The only "downside" is that you get the little alias stamp on the icon. It doesn't really matter to me if it's a symlink or a hard link. I can't see what either one offers over the other one (in this case). -David