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 12:33:20 -0700 [thread overview]
Message-ID: <e2de2b1f-c28e-96b0-8959-7de38e6df645@cs.ucla.edu> (raw)
In-Reply-To: <83blvessjj.fsf@gnu.org>
On 9/20/19 11:59 AM, Eli Zaretskii wrote:
> If we want to make such
> changes, we should do that in a way that caters to all the use cases
> we support today.
Of course. Among other things we should continue to let people access the
sources where they were originally built, if that's what they want to do. But
the default installation should be a safe one.
If it is considered to be too much to install the C source files by default, we
can simply make that an installation option with default off; that will still be
safe, since find-function-C-source-directory will do the right thing when the
source files are not installed. However, I'm mildly inclined to install the
source files by default since they don't grow the installation size that much:
on my platform the current default installation is 144 MiB, and the relevant
source files are 8.6 MiB uncompressed, 2.5 MiB compressed (these counts include
filesystem overhead).
> I asked what security problems could be caused by accessing a source tree
I'll reply separately about that.
next prev parent reply other threads:[~2019-09-20 19:33 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
2019-09-20 19:33 ` Paul Eggert [this message]
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=e2de2b1f-c28e-96b0-8959-7de38e6df645@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.