From: ludo@gnu.org (Ludovic Courtès)
To: Eli Zaretskii <eliz@gnu.org>
Cc: 20330@debbugs.gnu.org
Subject: bug#20330: Do not capture build-time $PATH in 'emacs' binary
Date: Wed, 15 Apr 2015 09:45:38 +0200 [thread overview]
Message-ID: <87mw2925st.fsf@gnu.org> (raw)
In-Reply-To: <83a8yabr79.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 14 Apr 2015 19:38:34 +0300")
Eli Zaretskii <eliz@gnu.org> skribis:
>> From: ludo@gnu.org (Ludovic Courtès)
>> Cc: 20330@debbugs.gnu.org
>> Date: Tue, 14 Apr 2015 18:10:27 +0200
>>
>> Eli Zaretskii <eliz@gnu.org> skribis:
>>
>> >> From: ludo@gnu.org (Ludovic Courtès)
>> >> Date: Tue, 14 Apr 2015 13:51:35 +0200
>> >>
>> >> The attached patch makes sure that the ‘emacs’ executable does not
>> >> capture the value of the build-time $PATH (which notably includes the
>> >> build directory, which may or may not exist afterwards.)
>> >
>> > Why only exec-path?
>>
>> AFAICS this is the only thing that captures the build-time $PATH in the
>> installed binary.
>
> What makes PATH special? Don't you want to prevent any build-time
> directories (except source-directory) from leaking into the binary?
I do, but I haven’t noticed any other leaks. Do you think there are
others?
Thanks,
Ludo’.
next prev parent reply other threads:[~2015-04-15 7:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 11:51 bug#20330: Do not capture build-time $PATH in 'emacs' binary Ludovic Courtès
2015-04-14 14:39 ` Eli Zaretskii
2015-04-14 16:10 ` Ludovic Courtès
2015-04-14 16:38 ` Eli Zaretskii
2015-04-15 7:45 ` Ludovic Courtès [this message]
2015-04-15 16:12 ` Eli Zaretskii
2015-04-15 16:37 ` Ludovic Courtès
2015-04-15 16:49 ` Eli Zaretskii
2015-04-15 17:07 ` Glenn Morris
2015-04-15 19:45 ` Ludovic Courtès
2015-04-16 15:37 ` Glenn Morris
2015-04-16 15:49 ` Eli Zaretskii
2015-04-16 19:25 ` Glenn Morris
2015-04-16 19:33 ` Eli Zaretskii
2015-04-20 21:48 ` Glenn Morris
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=87mw2925st.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=20330@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.