all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Michael Rohleder" <mike@rohleder.de>
To: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Install C source code for for debugging help
Date: Sat, 28 Sep 2019 04:14:19 +0200	[thread overview]
Message-ID: <87k19tb210.fsf@rohleder.de> (raw)
In-Reply-To: <4F3CD911-4F73-4C64-9EB5-23ED639E6DBB@gmail.com> (Fu Yuan's message of "Fri, 27 Sep 2019 18:45:07 -0400")

[-- Attachment #1: Type: text/plain, Size: 1284 bytes --]

Fu Yuan <casouri@gmail.com> writes:
> So what I’m trying to say is that 1) Emacs is already encouraging users to
> explore (Elisp) source and 2) enabling access to C by default don’t have much
> benefit and 3) there might be a good alternative.

To 3) one is to use gentoo (and maybe other source based distros?) which
have this functionality build in:

- build emacs with USE=sources and they get installed in
/usr/share/emacs/${FULL_VERSION}/src
- put FEATURES=installsources in your make.conf and sources
get installed to /usr/src/debug/${CATEGORY}/${PF}/${S#"${WORKDIR}/"}/src

etc (w/ symbols, git master branch ...)

For .deb based distros one can "apt-get source emacs.deb" after you have
added a deb-src url to /etc/apt/sources.list.


So in short, I think this is the job of a distro and also the freedom
for the user to decide if he wants src installed should be there
(or in the package management).

But, if its easy to add a ./configure flag like --install-with-sources,
it could still be useful, because it has much more information about
what exactly are the source files, so it could make (src) packaging
easier. (eg gentoo copies .c,.h,.m files. that could be wrong...)


-- 
Redistribution via the Microsoft Network is prohibited.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  parent reply	other threads:[~2019-09-28  2:14 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-26 20:37 Install C source code for for debugging help Paul Eggert
2019-09-27  5:07 ` Eli Zaretskii
2019-09-27  6:13   ` Paul Eggert
2019-09-27  7:19     ` Eli Zaretskii
2019-09-27 13:01       ` Stefan Monnier
2019-09-27 13:12         ` Stefan Monnier
2019-09-27 13:33         ` Eli Zaretskii
2019-09-27 13:48           ` Stefan Monnier
2019-09-27 13:56             ` Eli Zaretskii
2019-09-27 14:24               ` Paul Eggert
2019-09-27 14:40                 ` Eli Zaretskii
2019-09-28  4:03                   ` Paul Eggert
2019-09-27 17:04                 ` Noam Postavsky
2019-09-27 22:45                   ` Fu Yuan
2019-09-28  0:09                     ` Juanma Barranquero
2019-09-28  2:14                     ` Michael Rohleder [this message]
2019-09-27 15:25               ` Stefan Monnier
2019-09-28  1:32                 ` Richard Stallman
2019-09-28  2:06                   ` Jean-Christophe Helary
2019-09-27 15:03             ` Lars Ingebrigtsen
2019-09-27 15:47             ` David Ringo
2019-09-27  8:37     ` Andreas Schwab
2019-09-27  9:06       ` Eli Zaretskii
2019-09-27 11:58         ` Andreas Schwab
2019-09-27 12:58           ` Eli Zaretskii
2019-09-27 13:45             ` Andreas Schwab
2019-09-27 13:50               ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2019-09-28 18:19 Angelo Graziosi
2019-09-29  6:56 ` 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=87k19tb210.fsf@rohleder.de \
    --to=mike@rohleder.de \
    --cc=emacs-devel@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.