From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: Win32 GnuTLS DLL installer?
Date: Thu, 21 Sep 2017 13:33:40 -0400 [thread overview]
Message-ID: <87vakcc5xn.fsf@lifelogs.com> (raw)
In-Reply-To: 83fubgdm4y.fsf@gnu.org
On Thu, 21 Sep 2017 19:58:21 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Ted Zlatanov <tzz@lifelogs.com>
>> Date: Thu, 21 Sep 2017 11:38:01 -0400
>>
EZ> How do you define "outdated"? GnuTLS developers maintain 3 branches
EZ> in parallel, and release versions from all the 3 branches. Which one
EZ> should we follow, and does any N+1 release from that branch mean that
EZ> the N release is considered "outdated" and should be replaced?
>>
>> That's usually the platform's responsibility, but in this case it seems
>> up to us. I would keep up with the current branch (whatever was
>> installed already) at least, on the principle of least surprise.
EZ> So whenever the current branch sees a new release, someone would have
EZ> to port it to Windows and provide the binaries?
I'd check for the binaries that are actually available, so it wouldn't
do anything other than saying "hey there's a new DLL you should run."
And there would be no new process on the build side.
EZ> Moreover, accommodating a new version of GnuTLS might mean changes to
EZ> Emacs C and/or Lisp sources -- are we going to release patches to
EZ> the core sources through ELPA or something?
>>
>> Theoretically the current branch will not require that.
EZ> Theoretically, yes. In practice, this can and did happen.
You're right. I don't see a way around that except tracking version
compatibility in a security-patches package or repo OR accepting that
rare problem as a known and acceptable situation.
>> I would just post a non-intrusive message to the user for now.
EZ> Not sure how a message could help with source-level changes. People
EZ> who track the Git repository normally don't keep local patches.
EZ> People who use official releases don't even have the sources in most
EZ> cases.
Right. I'd just check the DLL binaries actually available.
A message would help the user determine that they should upgrade.
Ted
next prev parent reply other threads:[~2017-09-21 17:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 16:08 Win32 GnuTLS DLL installer? Ted Zlatanov
2017-09-20 20:15 ` Phillip Lord
2017-09-21 2:52 ` Sivaram Neelakantan
2017-09-21 11:19 ` Eli Zaretskii
2017-09-21 20:23 ` Phillip Lord
2017-09-21 14:28 ` Ted Zlatanov
2017-09-21 14:49 ` Eli Zaretskii
2017-09-21 15:38 ` Ted Zlatanov
2017-09-21 16:58 ` Eli Zaretskii
2017-09-21 17:33 ` Ted Zlatanov [this message]
2017-09-21 17:44 ` Eli Zaretskii
2017-09-21 17:57 ` Ted Zlatanov
2017-09-21 18:31 ` Eli Zaretskii
2017-09-21 21:16 ` Phillip Lord
2017-09-22 7:29 ` Eli Zaretskii
2017-09-21 21:13 ` Phillip Lord
2017-09-21 21:08 ` Phillip Lord
2017-09-22 12:44 ` Ted Zlatanov
2017-09-27 8:57 ` Jostein Kjønigsen
2017-11-20 19:41 ` Ted Zlatanov
2017-11-22 23:11 ` 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=87vakcc5xn.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).