From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Correct Paths to Emacs C Sources after Installation
Date: Tue, 04 Nov 2014 17:51:05 +0200 [thread overview]
Message-ID: <83vbmvufpy.fsf@gnu.org> (raw)
In-Reply-To: <CAKu-7WzAyt-qGJK1twtP+n_YvV_XWZh9STZ8jpsQqGdp-NJvug@mail.gmail.com>
> Date: Tue, 4 Nov 2014 16:33:54 +0100
> From: Alexander Shukaev <haroogan@gmail.com>
> Cc: help-gnu-emacs@gnu.org
>
> Furthermore, Eli told me recently that sources should be included
> (either separately or in the same archive) anyway to be compliant
> with the license.
I meant a separate source archive, of course. That had nothing to do
with having the sources installed, let alone in some specific public
place.
> Can you give "typical examples" where (expand-file-name "../src/emacs"
> > invocation-directory) will give the right result?
>
>
> Would you agree that this is *at least* more reasonable default in many
> cases than hard coding nonexistent directory?
No, it's much *less* reasonable.
> There were plenty of examples like relocating/deleting sources from
> original location where they were during build or moving to
> different machine with prebuilt Emacs (for instance on UFD) or
> distributing it as prebuilt package to other users. I don't know
> what other "more" convincing examples you want to find as these ones
> pretty much cover the use cases of "source-directory" variable.
Relocating things will not necessarily put them in ../src/ relative to
the binaries. There's any number of other places, so the probability
of winding up in ../src is close to zero.
next prev parent reply other threads:[~2014-11-04 15:51 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 [this message]
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
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=83vbmvufpy.fsf@gnu.org \
--to=eliz@gnu.org \
--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).