all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alexis <flexibeast@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Correct Paths to Emacs C Sources after Installation
Date: Tue, 04 Nov 2014 12:30:49 +1100	[thread overview]
Message-ID: <87wq7bu3rv.fsf@gmail.com> (raw)
In-Reply-To: <CAKu-7WxOjEnBe=dotV8GjyV13zT-2Npui6TiWTNg3zZxuv-5+g@mail.gmail.com>


Alexander Shukaev writes:

> Did you delete the build directory?

No, i didn't. In contrast to yourself, i don't usually delete my build
directories, because i might need to rebuild with some slight
modifications; deleting everything would result in the entire build
being done from scratch, often (from my point of view) unnecessarily.

> Furthermore, I just don't get what exactly you don't understand. Do
> you realize that the default `source-directory` is hard coded to the
> path where Emacs sources were when you built them? You cannot relocate
> them now without either manually changing the value of this variable
> through Emacs Lisp or rebuilding Emacs from scratch so that the
> default changes. This poses a major difficulty when distributing Emacs
> as a prebuilt package, since on the developer machine sources would be
> located on some directory which does not even exists for end
> users. How many more times should I repeat that issue?

Well, my apologies; i got confused because, even though your original
post implied (to me) that the packaging issue was your primary concern,
in a subsequent post you mentioned both the packaging issue /and/ the
case where you yourself were compiling - but i then overlooked the fact
that you delete your build directories. Sorry!

i'm not one of the Emacs maintainers, myself, but i would think this is
something that needs to be decided by those who package Emacs. Not all
those packaging Emacs have end-users who want or need the C sources to
be available, so from the point of view of such packagers, including the
sources in the package would make it unnecessarily large. Furthermore,
different platforms (e.g. different Linux distros) might differ in where
such C sources should be located in their filesystem hierarchy
(e.g. they might have chosen /usr/src/ as the standard location for C
sources). So it seems to me it might be best for the Emacs build system
to not make decisions best left to package maintainers.


Alexis.



  parent reply	other threads:[~2014-11-04  1:30 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wq7bu3rv.fsf@gmail.com \
    --to=flexibeast@gmail.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.
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.