From: David Caldwell <david@porkrind.org>
To: "Jan D." <jan.h.d@swipnet.se>
Cc: 19850@debbugs.gnu.org
Subject: bug#19850: 25.0.50; [PATCH] configure.ac: Fix site-lisp paths with NS self-contained apps.
Date: Sat, 14 Feb 2015 02:09:50 -0800 [thread overview]
Message-ID: <54DF1EEE.20604@porkrind.org> (raw)
In-Reply-To: <B706CA02-D0A8-4715-A2BB-2BC35A43A77C@swipnet.se>
[-- Attachment #1: Type: text/plain, Size: 2398 bytes --]
On 2/14/15 1:25 AM, Jan D. wrote:
>
> Also, /Library is in not the equivalent of /usr/local. /usr/local is the equivalent of /usr/local.
Not really. /usr/local is for unix command liney stuff, which Emacs
isn't really a part of once it becomes a self contained .app.
> /Library is a system directory, a mix of /etc and /usr/share. There are startup daemons there, fonts, internet plugins and so on. These things are not in /usr/local on any sane Unix-like OS.
/Library is not really a system directory, though the system does
install stuff there by default. You're right that it's a bit of a mix,
but it's also definitely got /usr/local leanings as well. Apple says
this about it [1]:
> /Library (OS X only)—Apps that share resources between users store those resources in this version of the Library directory.
So it's certainly OK to put site wide application stuff in /Library
(given that it's Apple's stated purpose). And I believe it's technically
100% kosher to delete anything in there. Nothing in there is critical to
the system running. The Fonts that actually matter are in
/System/Library/Fonts. That's not really here nor there though (but it's
why I said it's "not really" a system directory).
The question is why should Emacs not default to a reasonable, user
controlled site-wide place? And where should that place be?
I think it's worthwhile to take a look at what Perl does, because it's
one of the more fitting-in-est unix programs the Mac ships with. The
built-in Perl modules are in /System/Library/Perl. If you run 'cpan' and
install modules yourself, they go into /Library/Perl. Tcl is similar.
So what I'm proposing is not without precedent...
I believe if a Mac user saw that /Library/Application Support/Emacs or
/Library/Emacs in the load-path, they would not bat an eye, and would
completely understand under what circumstances they would add stuff there.
On the other hand, there's a bit of asymmetry since the user's config is
still ~/.emacs and not ~/Library/Application Support/Emacs (and I
wouldn't want that to change). Even so, I still think /Library is the
right place to default locallisppath.
-David
[1]
https://developer.apple.com/library/ios/documentation/FileManagement/Conceptual/FileSystemProgrammingGuide/FileSystemOverview/FileSystemOverview.html#//apple_ref/doc/uid/TP40010672-CH2-SW1
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4219 bytes --]
next prev parent reply other threads:[~2015-02-14 10:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 21:51 bug#19850: 25.0.50; [PATCH] configure.ac: Fix site-lisp paths with NS self-contained apps David Caldwell
2015-02-13 6:57 ` Jan D.
2015-02-13 7:28 ` David Caldwell
2015-02-13 13:41 ` Jan D.
2015-02-13 19:41 ` David Caldwell
2015-02-14 9:25 ` Jan D.
2015-02-14 10:09 ` David Caldwell [this message]
2015-02-13 16:36 ` Jan D.
2015-02-13 16:46 ` Jan D.
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54DF1EEE.20604@porkrind.org \
--to=david@porkrind.org \
--cc=19850@debbugs.gnu.org \
--cc=jan.h.d@swipnet.se \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.