From: phillip.lord@russet.org.uk (Phillip Lord)
To: Eli Zaretskii <eliz@gnu.org>
Cc: jostein@kjonigsen.net, jostein@secure.kjonigsen.net, emacs-devel@gnu.org
Subject: Re: windows installer
Date: Sat, 11 Nov 2017 11:24:09 +0000 [thread overview]
Message-ID: <87r2t53vom.fsf@russet.org.uk> (raw)
In-Reply-To: <83d14pp87b.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 11 Nov 2017 09:48:08 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: phillip.lord@russet.org.uk (Phillip Lord)
>> Cc: jostein@secure.kjonigsen.net, jostein@kjonigsen.net, emacs-devel@gnu.org
>> Date: Fri, 10 Nov 2017 23:27:49 +0000
>>
>> >> > environment-variables on my Windows 10 test-machine: USERPROFILE (or
>> >> > by concatenating HOMEDRIVE and HOMEPATH ).
>> >>
>> >> I'll fix this.
>> >
>> > Just to make this more complex: the Windows platform conventions frown
>> > upon installing stuff in that directory; you are supposed to create a
>> > subdirectory and install there.
>> >
>> > And programs should not end up there, they should be under
>> > %ProgramFiles% instead. The user's directory is for files, not for
>> > programs.
>>
>> The disadvantage with ProgramFiles is that it requires elevation, which
>> user profile does not, although user profiles gets mixed up with
>> roaming. Although, elevation is pretty normal for installation. But I
>> didn't want to it straight away in case I made the uninstaller
>> accidentally delete my windows installation.
>
> I don't think I understand the last sentence.
"didn't want to do it", sorry.
The installer includes an uninstaller which recursively deletes the
directory tree. If I get it wrong, AFAICT, it will delete anything I
tell it to. Being elevated seems a bad thing during development.
> For the rest, installing into the user's profile because doing TRT is
> harder is not a sufficient reason in my book. If you want to avoid
> elevation (which I don't think you should, given that this is "normal"
> Windows behavior nowadays), then install into a directory that is
> neither user profile nor Program Files (and maybe not even drive C:,
> if there is another drive). But going to the user profile is highly
> unusual, to say the least.
>
>> > They _will_ want to add it to PATH if they want to install packages
>> > from the likes of ELPA, which frequently come with Makefiles that
>> > invoke Emacs to compile the Lisp files.
>>
>> Really?
>
> AFAIU, yes.
I checked; the makefiles in ELPA are for the developers pleasure, not
users. The make file doesn't get pulled down, nor is it run client
side. MELPA is the same -- there is no build step from git source to end
package -- it's all just lisp.
> And even if ELPA packages have alternatives which don't invoke Make,
> there will be other situations where building a package with Emacs
> support will want to invoke Emacs. One such example is GNU ID-utils.
>
> IOW, Emacs is not just a GUI application used interactively, it is
> also a program that supports batch-mode invocation, and that mode is
> at times used by other programs. Keeping the Emacs binary off the
> users' system PATH is therefore less than ideal, because the users
> will then bump into subtle problems whereby Emacs seems "unavailable".
I suspect that these sort of users will install with the zip file or
equivalent.
Phil
next prev parent reply other threads:[~2017-11-11 11:24 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 23:11 windows installer Phillip Lord
2017-10-28 21:47 ` Richard Stallman
2017-11-06 8:11 ` Jostein Kjønigsen
[not found] ` <87h8u6bae3.fsf@russet.org.uk>
[not found] ` <WM!524810e63610127669556b68fb62cde560daf19be50fc52d4d63dd232af7bdb0490810e03b84a6559c9b2017d8462cc3!@mailhub-mx4.ncl.ac.uk>
2017-11-08 7:31 ` Jostein Kjønigsen
2017-11-10 17:01 ` Phillip Lord
2017-11-10 18:52 ` Eli Zaretskii
2017-11-10 20:46 ` Stefan Monnier
2017-11-10 21:22 ` John Mastro
2017-11-10 21:35 ` Fabrice Popineau
2017-11-11 7:33 ` Eli Zaretskii
2017-11-11 11:34 ` Phillip Lord
2017-11-11 14:57 ` Stefan Monnier
2017-11-12 11:21 ` Jostein Kjønigsen
2017-11-10 21:33 ` Fabrice Popineau
2017-11-11 7:35 ` Eli Zaretskii
2017-11-10 23:27 ` Phillip Lord
2017-11-11 0:25 ` Fabrice Popineau
2017-11-11 11:25 ` Phillip Lord
2017-11-12 0:30 ` Fabrice Popineau
2017-11-12 4:30 ` Eli Zaretskii
[not found] ` <87fu9hbytq.fsf@russet.org.uk>
2017-11-13 22:25 ` Phillip Lord
2017-11-14 13:08 ` Fabrice Popineau
2017-11-16 16:15 ` Phillip Lord
2017-11-11 7:48 ` Eli Zaretskii
2017-11-11 11:24 ` Phillip Lord [this message]
2017-11-11 12:01 ` Eli Zaretskii
[not found] ` <<83ineiotjr.fsf@gnu.org>
2017-11-10 21:43 ` Drew Adams
2017-11-10 23:35 ` Phillip Lord
2017-11-11 7:49 ` Eli Zaretskii
2017-11-11 7:40 ` Eli Zaretskii
2017-11-11 9:42 ` Yuri Khan
2017-11-11 10:37 ` Eli Zaretskii
2017-11-11 16:39 ` Drew Adams
[not found] ` <87a7zpbxza.fsf@russet.org.uk>
2017-11-13 22:44 ` Phillip Lord
2017-11-14 14:54 ` Drew Adams
2017-11-16 16:15 ` Phillip Lord
2017-11-16 16:23 ` Eli Zaretskii
2017-11-16 16:31 ` Fabrice Popineau
2017-11-16 16:57 ` Eli Zaretskii
2017-11-16 17:35 ` Fabrice Popineau
2017-11-16 17:39 ` Eli Zaretskii
2017-11-16 18:10 ` Fabrice Popineau
2017-11-16 20:45 ` Richard Copley
2017-11-17 7:14 ` Eli Zaretskii
2017-11-17 7:22 ` Fabrice Popineau
2017-11-17 7:35 ` Eli Zaretskii
2017-11-17 7:25 ` Fabrice Popineau
2017-11-16 17:42 ` Noam Postavsky
2017-11-16 17:45 ` Fabrice Popineau
2017-11-22 22:39 ` Phillip Lord
-- strict thread matches above, loose matches on Subject: below --
2017-11-12 8:56 Angelo Graziosi
2017-11-12 9:03 ` Fabrice Popineau
2017-11-12 11:30 ` Eli Zaretskii
2017-11-12 12:39 ` Fabrice Popineau
[not found] ` <8760adbxw6.fsf@russet.org.uk>
2017-11-13 22:46 ` Phillip Lord
2017-11-14 14:36 ` Angelo Graziosi
2017-11-14 16:31 ` Fabrice Popineau
2017-11-14 20:12 ` Angelo Graziosi
2017-11-20 8:46 ` Jostein Kjønigsen
2017-11-20 18:07 ` Eli Zaretskii
2017-11-22 23:01 ` Phillip Lord
2017-11-23 3:43 ` Eli Zaretskii
2017-11-23 18:06 ` Phillip Lord
2017-11-23 20:09 ` Eli Zaretskii
2017-11-24 19:13 ` Phillip Lord
2017-11-24 19:56 ` Eli Zaretskii
2017-11-25 11:08 ` Phillip Lord
2017-11-25 12:56 ` Eli Zaretskii
2017-11-27 17:56 ` Phillip Lord
2017-11-12 14:14 ` Angelo Graziosi
2017-11-12 11:28 ` Eli Zaretskii
2017-11-12 14:27 ` Angelo Graziosi
2017-11-12 15:04 ` Eli Zaretskii
2017-11-12 17:32 ` Angelo Graziosi
2017-11-12 18:42 ` 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=87r2t53vom.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jostein@kjonigsen.net \
--cc=jostein@secure.kjonigsen.net \
/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).