all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jostein@secure.kjonigsen.net, phillip.lord@russet.org.uk,
	jostein@kjonigsen.net, emacs-devel@gnu.org
Subject: RE: windows installer
Date: Sat, 11 Nov 2017 08:39:05 -0800 (PST)	[thread overview]
Message-ID: <e675486b-8ea3-40f0-aff8-a282d176022b@default> (raw)
In-Reply-To: <83efp5p8km.fsf@gnu.org>

> > I, for one, am not interested in "installing" any Emacs build
> > (Program Files etc.).  I use multiple builds from different
> > releases.  I don't even want anything added, by default, to
> > PATH.
> 
> Then you should be fine with just unzipping a zip file, because by
> default the Windows explorer does that into a separate directory.

Yes, I am fine with the delivered binaries.  I thought that
was clear, but thanks for making it explicit.

Such binaries used to be delivered more often.  If there
were a simple "push-button" command to create them locally,
which didn't require anything else, I might well take
advantage of that too.

> But this installer is not for people like you or me who know what they
> are doing and have special needs and requirements.

OK.  (But I do not know what I am doing wrt building Emacs
on Windows - I don't do that.)

My only "special needs and requirements" is the
ability to put the equivalent of what the delivered
Windows zip for a binary provides in any folder.

> It is primarily for the naïve (a.k.a. "newbie") who just want to be
> able to invoke the installer and get Emacs installed "correctly",
> meaning that Emacs is available to any other program running on the
> system.  And that means being installed where other programs are
> installed (which gives them additional protection by system-wide
> processes and features), and being on PATH.

That's fine.  But is it not the case that this "installer"
also _builds_ Emacs for Windows?  If not then apologies
for misunderstanding.  But if yes, couldn't that part
of what it provides be easily decoupled from the rest
of the "installing"?

If so, wouldn't that be a good thing?  Folks who don't
want to hassle with obtaining and installing whatever
tooling is necessary to build Emacs could build it
easily and so might follow Emacs development more
closely, potentially providing more timely feedback.

Just a thought.  As it is now, I wait until there is
a pretest or release before seeing what has changed
and reporting problems or offering suggestions.

I'm not saying that Emacs needs to do this.  I'm
asking whether (1) the build part is already being
done, as part of this "Windows intaller" and (2) if
so, whether it wouldn't make sense to offer the
build-only (not "install") part as an option.  IOW,
be able to produce the equivalent of the Windows
binaries that are uploaded for, say, a pretest.



  parent reply	other threads:[~2017-11-11 16:39 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
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 [this message]
     [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

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

  git send-email \
    --in-reply-to=e675486b-8ea3-40f0-aff8-a282d176022b@default \
    --to=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jostein@kjonigsen.net \
    --cc=jostein@secure.kjonigsen.net \
    --cc=phillip.lord@russet.org.uk \
    /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.