unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: emacs-devel@gnu.org
Subject: Re: Windows Installer for Emacs-27
Date: Wed, 20 Dec 2017 12:56:42 +0000	[thread overview]
Message-ID: <87ind1d0c5.fsf@russet.org.uk> (raw)
In-Reply-To: <87k1xvbqi2.fsf@lifelogs.com> (Ted Zlatanov's message of "Sat, 09 Dec 2017 15:22:45 -0500")

Ted Zlatanov <tzz@lifelogs.com> writes:
>>> Then it will be easier to implement something in Emacs to check for
>>> available updates on that platform by looking at that version.
>
> PL> Let me know if you don't have enough.
>
> Anything else we can do from Emacs to help the user would be good:
>
> * check signature of installer (ideally without GnuPG, since installing
>   that on W32 is not easy)

Actually, that's easy since windows does this
automatically. Unfortunately, it needs the binary to be signed. That's
straight-forward enough, although I would need a certificate to do this,
which isn't free (as in beer). The same issue also applies to the
binaries inside the installer (i.e. runemacs, emacs and the rest).

In the ideal world, I would like FSF to do this, after I upload. They
can check the GPG signature, then code sign the installer. But,
runemacs and emacs I would need to sign before packagaing I fear.


> * check what DLLs are out of date and will be updated by the installer

That would be harder, and ultimately would just be a big list of
everything that has changed.


> * look at the release notes for this installer

That I can do from the changelogs; happy to incorporate this when I can.

> I understand this is not necessarily easy, but it would be helpful to
> Emacs users on that platform. None of it is required, though. We can
> already start checking that URL for "the latest" if the user enables it.

Checking for "latest" is a little complex since I need to consider the
correct upgrade paths (so emacs-26 to snapshot is probably
wrong. emacs-27-snapshot to emacs-27 itself is probably
correct. snapshots to pre-releases -- tricky). But yes, can be done.

> Can you just look at that list and consider if any of it is feasible?







  reply	other threads:[~2017-12-20 12:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87lgjibagr.fsf@russet.org.uk>
2017-11-07 11:21 ` Windows Installer for Emacs-27 Phillip Lord
2017-11-20 19:39   ` Ted Zlatanov
2017-11-22 23:09     ` Phillip Lord
2017-12-09 20:22       ` Ted Zlatanov
2017-12-20 12:56         ` Phillip Lord [this message]
2017-12-20 13:41           ` Robert Pluim
2017-12-20 17:58             ` Phillip Lord

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=87ind1d0c5.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --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).