unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Angelo Graziosi <angelo.g0@libero.it>
To: emacs-devel@gnu.org
Subject: Re: Install C source code for for debugging help
Date: Sat, 28 Sep 2019 20:19:44 +0200 (CEST)	[thread overview]
Message-ID: <1618617534.103643.1569694784784@mail1.libero.it> (raw)

Eli Zaretskii wrote:

> To see whether this is a useful feature, we'd need a real user poll

I build Emacs from the emacs-master.tar.gz file produced by the Git repo and after the build I delete both the build tree and the tarball (*), so I do not see any usefulness to have the source. If I need it I can read it directly online from the Git repo, and if I need it to change something and test  I can download it. BTW, I often build without debug info so why should I have the need of source? Why you insist in creating "user-developer"?  Do you really think all user of a software product aim to read it source to understand how it work?

Please, let me know how to disable this if installed on master...

  Angelo

----
(*) Really I start to build on GNU/Linux Mint where the tar.gz is downloaded. Then I build for this OS and do also a nox build to be installed on WSL. Then the tar.gz is transferred on the Windows partition where a Windows build is done for W10 Pro 64. the result is installed also on a W10 Home 64.



             reply	other threads:[~2019-09-28 18:19 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-28 18:19 Angelo Graziosi [this message]
2019-09-29  6:56 ` Install C source code for for debugging help Paul Eggert
  -- strict thread matches above, loose matches on Subject: below --
2019-09-26 20:37 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
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

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=1618617534.103643.1569694784784@mail1.libero.it \
    --to=angelo.g0@libero.it \
    --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 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).