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: Thu, 12 Feb 2015 23:28:42 -0800 [thread overview]
Message-ID: <54DDA7AA.3060701@porkrind.org> (raw)
In-Reply-To: <C1F005FC-36F8-4B5F-A6E5-A81A46165EB6@swipnet.se>
[-- Attachment #1: Type: text/plain, Size: 1828 bytes --]
On 2/12/15 10:57 PM, Jan D. wrote:
> Hi.
>
> If we keep site-lis as it is, we can have several Emacs versions installed, with different site-lisp:s.
> Also, changing files in site-lisp does not require root priviliges.
If we keep things as they are now, the site lisp file points to a random
directory that doesn't exist! Take a look again:
>> "/Users/build/workspace/Emacs-Multi-Build/label/mavericks/emacs-source/nextstep/Emacs.app/Contents/Resources/share/emacs/24.4/site-lisp"
This Emacs was built on a different machine than the one it's running
on. My machine has no "build" user and therefore no "/Users/build"
directory.
I certainly cannot create that directory without being root.
> Your change breaks both those feaures.
No, it actually doesn't. First off, it only affects self contained
nextstep builds, which (as I described above) are currently totally busted.
Secondly, it doesn't preclude different site lisps for different
Emacsen. Here's the epaths.h line generated with my patch:
#define PATH_SITELOADSEARCH
"/Library/emacs/25.0.50/site-lisp:/Library/emacs/site-lisp"
That still ends up with the version in the site lisp path, so there can
multiple site lisps.
Yes, the site lisp path is in /Library which is root:wheel, but that is
the correct place to put site wide things on the Mac. If you want
non-site wide lisps, you can always edit your .emacs with no root
privileges. Thinking about it, I'm not sure why non-root is a good idea
for site wide stuff in the first place: On a multi-user system, it seems
like a security problem for one user to affect all the other user's
site-lisp. That *should* require root (like it does on linux).
> I don't think this is a good idea.
Please reconsider. This really seems like the correct fix to me.
-David
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4219 bytes --]
next prev parent reply other threads:[~2015-02-13 7:28 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 [this message]
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
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=54DDA7AA.3060701@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.