From: Eli Zaretskii <eliz@gnu.org>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: emacs-devel@gnu.org
Subject: Re: Win32 GnuTLS DLL installer?
Date: Thu, 21 Sep 2017 19:58:21 +0300 [thread overview]
Message-ID: <83fubgdm4y.fsf@gnu.org> (raw)
In-Reply-To: <87zi9ocbae.fsf@lifelogs.com> (message from Ted Zlatanov on Thu, 21 Sep 2017 11:38:01 -0400)
> 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.
So whenever the current branch sees a new release, someone would have
to port it to Windows and provide the binaries?
> 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.
Theoretically, yes. In practice, this can and did happen.
> I would just post a non-intrusive message to the user for now.
Not sure how a message could help with source-level changes. People
who track the Git repository normally don't keep local patches.
People who use official releases don't even have the sources in most
cases.
> EZ> IOW, this sounds like a major undertaking on our part, and I'm sure
> EZ> more and more issues will pop up as we consider the implications. I'm
> EZ> not sure we want to become a de-facto "distro" for MS-Windows users,
> EZ> as I don't think we have the resources, even if we have the desire.
>
> Agreed, I wasn't suggesting all of that. It does seem like a general
> Emacs update process may be more appropriate, like Cygwin does, but
> simple messaging is a lot easier and less risky.
Again, I'm not sure I see how a message would help. And Cygwin does
produce packages as GNU/Linux distribution do, something I don't think
we should take upon ourselves.
next prev parent reply other threads:[~2017-09-21 16:58 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 [this message]
2017-09-21 17:33 ` Ted Zlatanov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83fubgdm4y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tzz@lifelogs.com \
/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.