From: Richard Copley <rcopley@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 14513@debbugs.gnu.org
Subject: bug#14513: 24.3.50; Site load-path pieces differ in MSYS build
Date: Tue, 4 Jun 2013 21:14:10 +0100 [thread overview]
Message-ID: <CAPM58oh91-8CW35guhEjT=WpqRUDYawkwpSkoQ_4xZG_P_0w6w@mail.gmail.com> (raw)
In-Reply-To: <838v2pwtu5.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1660 bytes --]
On 4 June 2013 20:37, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Tue, 4 Jun 2013 19:27:50 +0100
> > From: Richard Copley <rcopley@gmail.com>
> >
> > One last time I'll advocate the change I was thinking of initially:
> re-add
> > the "ROOT/../site-lisp" entry to PATH_SITELOADSEARCH in epaths.nt, as in
> > the attached patch.
>
> I hear you, but please understand: it's not just addition of a
> directory to the variable. These directories are tested for existence
> at startup, and Emacs displays a warning of any of them doesn't exist.
> So, if the Windows build had a directory that other builds don't, we
> would need Windows-specific code to ignore this specific directory if
> it doesn't exist, or make sure it is created -- only on Windows -- at
> "make install" time. And since this list of directories is
> constructed in a very convoluted way, paying attention to
> EMACSLOADPATH in the environment and to whether Emacs is run
> uninstalled, it is not easy to identify that single directory and
> ignore it.
>
> All this flies in the face of the main reason why I made the MSYS
> build happen: remove as much Windows specific issues, code, and
> configury, so that other developers and maintainers could understand
> how the Windows port is built, and could make changes without fear
> they break the Windows port too easily. If we don't stick to this
> attitude, the Windows port is in real danger of falling by the wayside
> at the slightest change of fortunes.
>
Okay, I can swallow that, thanks for the explanation.
Would it be doable and generally useful to take account of an
EMACSSITELOADPATH environment variable, on all platforms?
[-- Attachment #2: Type: text/html, Size: 2200 bytes --]
next prev parent reply other threads:[~2013-06-04 20:14 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 13:46 bug#14513: 24.3.50; Site load-path pieces differ in MSYS build Richard Copley
2013-05-30 16:40 ` Eli Zaretskii
2013-05-30 17:56 ` Richard Copley
2013-05-30 18:20 ` Eli Zaretskii
2013-05-30 19:02 ` Achim Gratz
2013-05-30 19:16 ` Eli Zaretskii
2013-05-30 19:57 ` Achim Gratz
2013-05-30 20:39 ` Eli Zaretskii
2013-05-30 21:21 ` Stefan Monnier
2013-05-31 19:01 ` Achim Gratz
2013-05-31 19:24 ` Eli Zaretskii
2013-05-30 19:06 ` Stefan Monnier
2013-05-30 19:18 ` Eli Zaretskii
2013-05-30 19:20 ` Richard Copley
[not found] ` <CAPM58ojwzkw8kxKc8P4G0mdsJgmYmo-ZxSbcN1F2J+QVyFaHMw@mail.gmail.com>
2013-05-30 19:29 ` Eli Zaretskii
2013-05-30 20:00 ` Stefan Monnier
2013-05-30 20:42 ` Eli Zaretskii
2013-05-30 21:43 ` Stefan Monnier
2013-05-31 6:20 ` Eli Zaretskii
2013-05-31 9:52 ` Richard Copley
2013-05-31 11:35 ` Eli Zaretskii
2013-05-31 12:55 ` Richard Copley
2013-06-01 16:04 ` Richard Copley
2013-06-01 16:38 ` Eli Zaretskii
2013-06-01 17:06 ` Richard Copley
[not found] ` <CAPM58og6ySbmR28vQH+m7dp-zYgVwrrYqthO6_ZfGodV9Si23w@mail.gmail.com>
[not found] ` <8361xx20lb.fsf@gnu.org>
2013-06-01 18:00 ` Richard Copley
2013-06-02 11:33 ` Richard Copley
2013-06-04 18:27 ` Richard Copley
2013-06-04 19:37 ` Eli Zaretskii
2013-06-04 20:14 ` Richard Copley [this message]
2013-06-04 20:21 ` Glenn Morris
2013-06-07 8:14 ` Eli Zaretskii
2013-06-07 17:48 ` Richard Copley
2013-06-04 23:55 ` Juanma Barranquero
2013-06-06 15:37 ` Eli Zaretskii
2013-06-07 1:49 ` Juanma Barranquero
2013-06-07 6:51 ` Eli Zaretskii
[not found] ` <83ip20469l.fsf@gnu.org>
2013-05-30 19:29 ` bug#14514: Fwd: " Richard Copley
2013-05-30 19:49 ` bug#14513: " Richard Copley
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='CAPM58oh91-8CW35guhEjT=WpqRUDYawkwpSkoQ_4xZG_P_0w6w@mail.gmail.com' \
--to=rcopley@gmail.com \
--cc=14513@debbugs.gnu.org \
--cc=eliz@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.