From: Stephen Leake <stephen_leake@member.fsf.org>
To: emacs-devel@gnu.org
Subject: Re: Directory structure changes in Emacs installed on MS-Windows
Date: Thu, 04 Apr 2013 19:03:41 -0400 [thread overview]
Message-ID: <85obdtlwz6.fsf@member.fsf.org> (raw)
In-Reply-To: <83r4iqfaw1.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 04 Apr 2013 20:45:02 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> As part of my work on building the native MS-Windows Emacs using the
> Posix configury and Makefile's, I intend to change the structure of
> the installed Emacs directory tree, so that it more closely resembles
> installations on Posix systems. The details are below.
>
>
> Does anyone see any disadvantages in making these changes?
I gather we will just need %emacs_dir%/bin in Windows PATH (as we need
now), not also %emacs_dir%/libexec/emacs/VERSION/i686-pc-mingw32 (emacs
will put the latter in exec-path by default).
If that's true, then I see no problem.
> The advantages of this arrangement, as I see them, are
You left out:
(0) it simplifies the task of using the Posix configury
I think that's important.
> (1) it follows the installation tree on Posix platforms, so will make
> things easier for those who work on both kinds of platforms;
Yes, but only minimally. I work on both platforms currently, and have
never noticed that the Windows install was non-standard.
I think that's because Posix doesn't have %emacs_dir% as the root, so I
already think of Windows as being "just different".
> (2) it will become possible to have several Emacs versions installed
> that can be invoked without any need to tweak PATH or rename the DOC
> file;
I don't follow this; there is only one place for emacs.exe. Currently I
handle this by using a different %emacs_dir% for each emacs version.
I guess you could have %emacs_dir%/bin/emacs-VERSION.exe ? Does the
Posix install do that (I've seen that convention for some tools).
When I install an alternate Emacs version on a Posix system, I put it in
/usr/local/bin, with the original in /usr/bin.
--
-- Stephe
next prev parent reply other threads:[~2013-04-04 23:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 17:45 Directory structure changes in Emacs installed on MS-Windows Eli Zaretskii
2013-04-04 22:51 ` Xue Fuqiao
2013-04-04 23:03 ` Stephen Leake [this message]
2013-04-05 6:06 ` Eli Zaretskii
2013-04-05 8:48 ` chad
2013-04-05 9:18 ` Eli Zaretskii
2013-04-05 13:19 ` Stefan Monnier
2013-04-05 14:18 ` Eli Zaretskii
2013-04-05 15:19 ` Stefan Monnier
2013-04-05 15:20 ` Glenn Morris
2013-04-05 17:32 ` chad
2013-04-04 23:16 ` Andy Moreton
2013-04-05 6:08 ` 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=85obdtlwz6.fsf@member.fsf.org \
--to=stephen_leake@member.fsf.org \
--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).