emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MacOSX installation suggestions.


From: Steven Tamm
Subject: Re: MacOSX installation suggestions.
Date: Sun, 5 Jan 2003 23:21:31 -0800


On Sunday, January 5, 2003, at 04:26  AM, Jan D. wrote:

Hello.

In the mac/INSTALL file it says twice that make install must be made as
root.  This is an error, I have never done make install as root, and
if you just have write permission, this works fine (as it does with
the other Emacs configurations).  I dont think documentation casually
should require you to be root to install things, when no such
requirement exists.  It discurages the installation of Emacs under
your own user.  I would change that to "make install requires that
you have write permission in the destination directories" or something
like that.  Or not write anything at all.

It depends on the configuration. If the configuration is to place it into /usr/local, then the correct permissions are there. However on my machine, the non-root user doesn't have permission to write into /usr/share, which would cause the installation to fail. Moreover, installing into /usr is probably not the best idea because Apple's system updates have a nasty habit of overwriting them (as it did between 10.1 and 10.2).

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.

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.

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).

-Steven





reply via email to

[Prev in Thread] Current Thread [Next in Thread]