From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
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 21:59:12 +0300 [thread overview]
Message-ID: <83blvessjj.fsf@gnu.org> (raw)
In-Reply-To: <43882d66-5955-add5-48b5-ea46333832ef@cs.ucla.edu> (message from Paul Eggert on Fri, 20 Sep 2019 11:17:43 -0700)
> Cc: tino.calancha@gmail.com, 37445@debbugs.gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Fri, 20 Sep 2019 11:17:43 -0700
>
> 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?
Yes. Help uses that when you activate the button in a *Help* buffer
that says a function is defined in C sources.
> 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.
You are talking about a serious change in Emacs installation
procedure. It should first be discussed and its various implications
understood and considered. I'm not so sure this is a good approach,
or that it should be the only one supported. Some people may not want
to install sources; others still build their own Emacs, and have the
sources available in accessible directories, so installing the sources
into yet another tree will be uneconomical for them. And there might
be other use cases and other considerations. If we want to make such
changes, we should do that in a way that caters to all the use cases
we support today.
I asked what security problems could be caused by accessing a source
tree, and you didn't answer. From where I stand, that is a crucial
question: if the danger is not real, or non-existent, I see no good
reason to make such significant changes, certainly not soon.
next prev parent reply other threads:[~2019-09-20 18:59 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
2019-09-20 18:59 ` Eli Zaretskii [this message]
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
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=83blvessjj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=37445@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--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 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).