From: Bob Proulx <bob@proulx.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Correct Paths to Emacs C Sources after Installation
Date: Tue, 4 Nov 2014 14:00:25 -0700 [thread overview]
Message-ID: <20141104135320983572700@bob.proulx.com> (raw)
In-Reply-To: <CAKu-7Wyfnt7U1wdXKcKDRbdX8wCgS5S0hdQySGLae9Z8-ZhmGA@mail.gmail.com>
Alexander Shukaev wrote:
> > I really don't think it is. The only thing I have ever seen use /usr/src
> > on GNU/Linux machines is the Linux kernel and other related items where
> > the sources are needed for compiling kernel modules.
>
> Perhaps you should look into "/usr/local/src". This is the place where
> package managers can fetch the so-called "source packages", those which
> contain only the source code.
The /usr/local tree won't be used directly by package managers.
Talking dpkg and rpm specifically here. The /usr/local tree is for
the local admin to do with as they will. (PATH variables such as
Perl's INC and others may include /usr/local paths so that packaged
tools integrate into the packaged tools installed into system
directories.) If you want it installed by a package manager then the
/usr/share/emacs/VERSION directory is about the only acceptable place
for it.
Personally I always felt that if you want to look at the source code
then it makes the most sense to download source and compile it. In
which case source will be wherever you have placed it. In my case
that is in my ~/src/foo directory tree. Being my own copy it means I
can make modifications and compile those modifications. Having
modified it means that I want it in version control so that I can use
it for diff'ing, for branching, generating patches, and general source
control.
Bob
next prev parent reply other threads:[~2014-11-04 21:00 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 20:55 Correct Paths to Emacs C Sources after Installation Alexander Shukaev
2014-11-03 20:58 ` Eli Zaretskii
[not found] ` <CAKu-7Ww3nzB3SQmKpR73xSVoC=U1Tf5UaJCokm4fpBvMSqAoNQ@mail.gmail.com>
2014-11-03 21:31 ` Fwd: " Alexander Shukaev
2014-11-03 22:27 ` Alexander Shukaev
2014-11-03 22:45 ` Stefan Monnier
2014-11-03 23:05 ` Alexander Shukaev
2014-11-04 0:24 ` John Mastro
2014-11-04 0:35 ` Alexander Shukaev
2014-11-04 0:52 ` Alexis
2014-11-04 1:11 ` Alexander Shukaev
2014-11-04 1:17 ` Alexander Shukaev
2014-11-04 1:21 ` Alexander Shukaev
2014-11-04 1:26 ` Alexander Shukaev
2014-11-04 1:30 ` Alexis
2014-11-04 12:20 ` Alexander Shukaev
2014-11-04 8:53 ` Thien-Thi Nguyen
2014-11-04 15:47 ` Eli Zaretskii
2014-11-04 15:02 ` Stefan Monnier
2014-11-04 15:33 ` Alexander Shukaev
2014-11-04 15:51 ` Eli Zaretskii
2014-11-04 16:07 ` Alexander Shukaev
2014-11-04 16:18 ` Alexander Shukaev
2014-11-04 16:48 ` Eli Zaretskii
2014-11-04 16:26 ` Eli Zaretskii
[not found] ` <mailman.12770.1415117275.1147.help-gnu-emacs@gnu.org>
2014-11-04 17:48 ` Stefan Monnier
2014-11-04 18:39 ` Alexander Shukaev
2014-11-04 18:57 ` Glenn Morris
2014-11-04 19:20 ` Alexander Shukaev
2014-11-04 21:00 ` Bob Proulx [this message]
2014-11-05 2:43 ` Yuri Khan
[not found] ` <mailman.12848.1415155389.1147.help-gnu-emacs@gnu.org>
2014-11-05 14:26 ` Ted Zlatanov
2014-11-05 2:07 ` Stefan Monnier
[not found] ` <mailman.12847.1415153254.1147.help-gnu-emacs@gnu.org>
2014-11-07 4:17 ` Jason Rumney
[not found] ` <mailman.12759.1415115240.1147.help-gnu-emacs@gnu.org>
2014-11-04 17:41 ` Stefan Monnier
2014-11-04 15:45 ` Eli Zaretskii
2014-11-04 15:43 ` Fwd: " 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=20141104135320983572700@bob.proulx.com \
--to=bob@proulx.com \
--cc=help-gnu-emacs@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.
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).