From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 37445@debbugs.gnu.org, tino.calancha@gmail.com
Subject: bug#37445: 27.0.50; Permission denied after make install
Date: Fri, 20 Sep 2019 11:17:43 -0700 [thread overview]
Message-ID: <43882d66-5955-add5-48b5-ea46333832ef@cs.ucla.edu> (raw)
In-Reply-To: <83woe3rvhg.fsf@gnu.org>
On 9/20/19 5:40 AM, Eli Zaretskii wrote:
> If you point source-directory away of where the real sources are, some
> Help features will cease working.
Which Help features are those? The files that Help uses are already installed
into the etc or lisp subdirectories of /usr/share/emacs/27.0.50 (or whatever).
I looked through the Emacs source code, and the only use of source-directory
that seemed relevant was find-function-C-source-directory; is that what you were
referring to? If so, the problem can be addressed by installing the C sources
into /usr/share/emacs/27.0.50/src/*.[chm], which is something we should be doing
anyway since the build directory might be missing or (worse) wrong when someone
wants to look at the sources of the installed Emacs. In the old days installing
the C sources might have been thought too heavyweight but those days are long gone.
next prev parent reply other threads:[~2019-09-20 18:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 9:02 bug#37445: 27.0.50; Permission denied after make install Tino Calancha
2019-09-18 19:12 ` Paul Eggert
2019-09-19 6:57 ` Paul Eggert
2019-09-19 11:35 ` Tino Calancha
2019-09-19 17:41 ` Paul Eggert
2019-09-20 6:07 ` Tino Calancha
2019-09-20 7:00 ` Eli Zaretskii
2019-09-20 9:10 ` Paul Eggert
2019-09-20 12:40 ` Eli Zaretskii
2019-09-20 18:17 ` Paul Eggert [this message]
2019-09-20 18:59 ` Eli Zaretskii
2019-09-20 19:33 ` Paul Eggert
2019-09-21 6:07 ` Eli Zaretskii
2019-09-26 20:11 ` Paul Eggert
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=43882d66-5955-add5-48b5-ea46333832ef@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=37445@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=tino.calancha@gmail.com \
/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.