unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Steven Tamm <steventamm@mac.com>
Cc: emacs-devel@gnu.org
Subject: Re: Mac OS X GNU Emacs Installer (make-package)
Date: Mon, 2 Dec 2002 11:22:03 -0800 (PST)	[thread overview]
Message-ID: <416771.1038856923730.JavaMail.steventamm@mac.com> (raw)

>Hi Steven,
>
>Actually the idea (which hasn't been implemented) was to have `make
>install' install only one executable on the entire system: the one in
>the Emacs.app application bundle.  Then /usr/local/bin/emacs would be
>the shell script:
>
>#!/bin/sh
>/Applications/Emacs.app/Contents/MacOS/Emacs "$@"
>

Actually, I think this is a good idea, but in the reverse.  I would have the single copy of the executable in /usr/local/bin/emacs and have the Emacs executable be a link (either sym or hard).  The main reason is that it is likely to have the application move, but extremely unlikely that /usr/local/bin/emacs would move.

I have a patch that tests if -nw is not specified and we are not in an application bundle (i.e. in /usr/local/bin/emacs), then fork and execute /Applications/Emacs.app/...   This makes the behavior from the command line more desirable.  The downside (as David) is that it will be confusing for most Mac users.  Two or more emacs executables will be running at the same time with each appearing in the dock as a separate icon.  This behavior is better than the current one, and using Launch Services, we can find the location of the Emacs application without resorting to hard coding or using libexec.

The behavior I would like to have the command line appear to act more like emacsclient (or more appropriately the gnuclient from the NT port).  The gnuclient port will, by default, instantiate emacs if one does not exist, something you need to do set by hand with emacsclient.  It would also require that the server is started, which is questionable.

>I don't have a strong preference to implement package distribution one
>way or another.  But I was considering the different options one can
>specify for make-package, which will result in the quite a few
>differently-configured packages people can distribute.  I also think
>some of the options are not achievable by people building from source
>using `make', which is a little strange.  Imagine the amount of
>questions we'll be getting :-).

I think I'll add in some documentation detailing about what to do.  After all the discussions on version tracker, I think a "strong" admonition about not using --prefix=/usr should be included (since, at least on my system, /usr/bin/emacs has been destroyed by system updates twice).

>I've also remove mac/make-bin-dist and mac/osx-install, which are
>obsolete now.  Perhaps we should mention make-package in mac/INSTALL.

I'll add in an explanation of make-package today.

On another note, I'm probably going to put in an #ifdef in terminfo.c to remove the redefinition of UP, BC, & PC on darwin 6.2.  This will fix some linking warnings.  This test should probably should be placed in configure.in.  Something like this:

AC_MSG_CHECKING(whether termcap global variables are defined externally)
AC_TRY_LINK([extern char *UP;],[*UP=0],[termcap_global_vars_extern=yes],[termcap_global_vars_extern=no])


-Steven

             reply	other threads:[~2002-12-02 19:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-02 19:22 Steven Tamm [this message]
2002-12-02 19:45 ` Mac OS X GNU Emacs Installer (make-package) Andrew Choi
  -- strict thread matches above, loose matches on Subject: below --
2002-11-30 22:23 Steven Tamm
2002-11-30 22:38 ` Kai Großjohann
2002-11-30 22:48 ` David Caldwell
2002-11-30 23:19   ` Steven Tamm
2002-11-30 23:50     ` David Caldwell
2002-12-01  1:53       ` Steven Tamm
2002-12-01  2:04         ` Miles Bader
2002-12-01  2:23           ` Steven Tamm
2002-12-02 15:46           ` Richard Stallman
2002-12-01  3:38         ` David Caldwell
2002-12-02 18:26     ` Andrew Choi
2002-12-02 15:46   ` Richard Stallman
2002-12-02 15:46 ` Richard Stallman
2002-12-02 16:04 ` Stefan Monnier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=416771.1038856923730.JavaMail.steventamm@mac.com \
    --to=steventamm@mac.com \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).