unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan D." <jan.h.d@swipnet.se>
Cc: emacs-devel@gnu.org
Subject: Re: MacOSX installation suggestions.
Date: Mon, 6 Jan 2003 12:07:37 +0100	[thread overview]
Message-ID: <1089BE0E-2167-11D7-A5BA-00039363E640@swipnet.se> (raw)
In-Reply-To: <7A846F7B-2147-11D7-91D4-00039390AB82@mac.com>

> The point is taken.  I will point out that if installing into /usr (or 
> possibly some other directory), one might need to use sudo.  I'll also 
> document the suggestion about not using /usr.

Thanks.

>> I do think make install should install Emacs.app also.  Now one has to
>> manually copy it after make install.  It doesn't seem right that make
>> install doesn't install everything.
>
> Makes sense.  I just put in some changes to get the Application to build 
> in a separate directory, so having it install into /Application would be 
> nice (and pretty much done); it would make the make-package script a 
> little easier.

I would like to suggest a separate configure option, that defaults to
/Application (--appdir?).  If doing a build and install as a regular
user, one probably don't wan't it in /Application.


> What do people think about placing this mac-specfic stuff in a new 
> Makefile in the mac/ directory v placing it in the src/ directory?  I was 
> just going to place it in the src directory because it's not large enough 
> to justify all the configuration changes needed (unless there are 
> volunteers).

Would a make in src call the Makefile in the mac directory?

	Jan D.

  reply	other threads:[~2003-01-06 11:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-05 12:26 MacOSX installation suggestions Jan D.
2003-01-06  7:21 ` Steven Tamm
2003-01-06 11:07   ` Jan D. [this message]
2003-01-07  5:52     ` Steven Tamm
2003-01-07 17:54       ` Jan D.
2003-01-06 21:51 ` Andrew Choi

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=1089BE0E-2167-11D7-A5BA-00039363E640@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --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).