From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: stefan@marxist.se, michael.albinus@gmx.de, 37527@debbugs.gnu.org
Subject: bug#37527: [PATCH] Install C source code for for debugging help
Date: Sun, 26 Jan 2020 21:24:35 +0200 [thread overview]
Message-ID: <83v9oynhqk.fsf@gnu.org> (raw)
In-Reply-To: <67c4c197-7c4f-0e02-366d-efa610bfc8cc@cs.ucla.edu> (message from Paul Eggert on Sun, 26 Jan 2020 10:18:38 -0800)
> Cc: stefan@marxist.se, michael.albinus@gmx.de, rgm@gnu.org,
> 37527@debbugs.gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Sun, 26 Jan 2020 10:18:38 -0800
>
> On 1/26/20 8:13 AM, Eli Zaretskii wrote:
> > they are both unreliable
>
> Only if we make them so. As things stand, emacs-source-directory is more
> reliable than source-directory is, and if we remove the configure-time option to
> omit installation of source code (a step I favor) we will make
> emacs-source-directory even more reliable than it is now.
>
> It's long past time that we stopped making Emacs source code a second-class
> citizen. The GNU philosophy is that it should be easy to see the source, and we
> should be guided by that philosophy here.
>
> We cannot rely on distributors to make things easy here. Some distributors do
> not install source; others install it in different places, only optionally, and
> do so in obscure ways that most users don't know about. Distributors will follow
> our lead if we install the source in a well-specified place. If we tried instead
> to find the nook or cranny (if any) where the current distributor squirrels away
> the Emacs source code, this problem would continue to be a maintenance headache
> for us. It's not worth the hassle.
Sorry, I cannot be convinced by reiterating the same views and
high-level abstract ideas. We had a discussion, where no consensus
was reached about making this the default. I don't see why would you
decide to unilaterally override all those valid opinions to the
contrary. Please make this opt-in.
next prev parent reply other threads:[~2020-01-26 19:24 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 20:07 bug#37527: [PATCH] Install C source code for for debugging help Paul Eggert
2019-09-27 5:09 ` Eli Zaretskii
2019-09-27 6:24 ` Paul Eggert
2019-09-27 7:21 ` Eli Zaretskii
2019-09-27 8:48 ` Andreas Schwab
2019-09-27 8:58 ` Michael Albinus
2019-09-27 11:36 ` Eli Zaretskii
2019-09-27 19:59 ` Michael Albinus
2019-09-28 5:55 ` Paul Eggert
2019-09-28 7:29 ` Eli Zaretskii
2019-09-28 7:54 ` Michael Albinus
2019-09-29 7:09 ` Paul Eggert
2019-09-28 6:01 ` Eli Zaretskii
2019-09-28 9:11 ` Michael Albinus
2019-09-28 9:43 ` Eli Zaretskii
2019-10-03 13:38 ` Michael Albinus
2019-10-03 16:26 ` Eli Zaretskii
2019-10-04 8:52 ` Michael Albinus
2019-10-03 16:54 ` Basil L. Contovounesios
2019-10-04 8:54 ` Michael Albinus
2019-10-03 21:50 ` Paul Eggert
2019-10-03 22:32 ` Glenn Morris
2019-10-04 1:28 ` Paul Eggert
2019-10-04 8:57 ` Michael Albinus
2019-10-04 9:20 ` Michael Albinus
2019-10-06 7:48 ` Paul Eggert
2019-10-07 15:17 ` Michael Albinus
2019-10-07 19:48 ` Paul Eggert
2019-10-08 7:47 ` Eli Zaretskii
2019-10-08 9:54 ` Michael Albinus
2019-10-08 11:58 ` Eli Zaretskii
2020-01-20 19:12 ` Stefan Kangas
2020-01-21 9:13 ` Paul Eggert
2020-01-21 17:02 ` Eli Zaretskii
2020-01-21 17:48 ` Paul Eggert
2020-01-21 18:04 ` Eli Zaretskii
2020-01-22 0:27 ` Paul Eggert
2020-01-22 3:31 ` Eli Zaretskii
2020-01-23 8:58 ` Paul Eggert
2020-01-23 14:23 ` Eli Zaretskii
2020-01-23 17:42 ` Paul Eggert
2020-01-23 18:24 ` Eli Zaretskii
2020-01-25 0:47 ` Paul Eggert
2020-01-25 7:58 ` Eli Zaretskii
2020-01-26 9:00 ` Paul Eggert
2020-01-26 16:13 ` Eli Zaretskii
2020-01-26 18:18 ` Paul Eggert
2020-01-26 19:24 ` Eli Zaretskii [this message]
2020-01-26 20:09 ` Michael Albinus
2020-01-27 21:17 ` Paul Eggert
2020-01-28 3:22 ` Eli Zaretskii
2020-01-26 20:06 ` Michael Albinus
2020-01-26 20:10 ` Eli Zaretskii
2019-09-28 5:51 ` Paul Eggert
2019-09-29 13:02 ` Rohan Hendrik Jotz-Lean
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=83v9oynhqk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=37527@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=michael.albinus@gmx.de \
--cc=stefan@marxist.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.