unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Christoph Scholtes <cschol2112@googlemail.com>
Cc: Ted Zlatanov <tzz@lifelogs.com>, Eli Zaretskii <eliz@gnu.org>,
	Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: bug#10612: GnuTLS bundled with the windows Emacs binaries
Date: Sun, 29 Jan 2012 18:26:57 +0100	[thread overview]
Message-ID: <CAAeL0SS+K0pW1KTcoVeVf5j-VnsoexNoY_CxMqBAg9=0yH8bvw@mail.gmail.com> (raw)
In-Reply-To: <4F257D1F.5050105@gmail.com>

On Sun, Jan 29, 2012 at 18:08, Christoph Scholtes
<cschol2112@googlemail.com> wrote:

> Why is that?

Because the number of Windows machines with a compiler and a build
environment is almost zero, and though they are available (and free)
the average Windows users knows nothing about them and wouldn't know
how to (or be interested in) install and use them.

It's been said a few times here, by RMS and others, than providing
Emacs for Windows (binary or not) is intended to be a bridgehead to
introduce users of non-free software to the advantages of free
software (not to facilitate them using Windows). If we didn't offer
binaries for Windows, almost nobody would use it. It's politically
convenient to provide them.

> I agree, but doesn't that also start with compiling support for GnuTLS into
> the prebuilt Emacs?

No. That's just an enabler. Whether they use it or not is their
decision, and they should be aware of the risks and benefits before
doing it.

> If  there is a security update for GnuTLS that requires the user to use the
> latest certain version, don't we have to provide support for the latest
> version in the binary?

Yes, but bugs that force a change in the API are less frequent. Of
course as soon as we add some capability we expose the user to
security risks (23.4 wouldn't be needed without EDE). We have to put
the line at some point.

And, in any case, bearing the responsibility of the upgrades isn't my
main objection, and never has, just another inconvenience. The main
argument is still that GnuTLS, etc. have their own projects and
maintainers, and they should be the ones taking care of building and
distributing it.

    Juanma



  reply	other threads:[~2012-01-29 17:26 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <84boromyob.fsf@tum.de>
     [not found] ` <m3lipk5scv.fsf@stories.gnus.org>
     [not found]   ` <84ipknew07.fsf@tum.de>
     [not found]     ` <87ipjzs512.fsf@gnus.org>
2012-01-26 15:44       ` bug#10612: GnuTLS bundled with the windows Emacs binaries (was: bug#10215: 24.0.92; Can't contact nnimap (gnutls-cli not found)) Ted Zlatanov
2012-01-26 15:15         ` Juanma Barranquero
2012-01-26 19:32           ` bug#10612: GnuTLS bundled with the windows Emacs binaries Ted Zlatanov
2012-01-26 19:36             ` [h-e-w] " Eli Zaretskii
2012-01-26 21:07               ` Ted Zlatanov
2012-01-26 21:39                 ` Eli Zaretskii
2012-01-27 15:59                   ` Ted Zlatanov
2012-01-27 15:30                     ` Juanma Barranquero
2012-01-30 12:59                       ` Ted Zlatanov
2012-01-27 15:45                     ` Eli Zaretskii
2012-01-26 22:53                 ` Juanma Barranquero
2012-03-17 15:41           ` Uday S Reddy
2012-03-17 18:11             ` Eli Zaretskii
2012-03-22 18:38             ` Lars Magne Ingebrigtsen
2014-12-08 20:05           ` Lars Magne Ingebrigtsen
2014-12-08 20:31             ` Drew Adams
2014-12-08 20:50             ` Eli Zaretskii
2014-12-08 20:56               ` Lars Magne Ingebrigtsen
2014-12-08 21:10                 ` Óscar Fuentes
2014-12-08 21:24                   ` Lars Magne Ingebrigtsen
2016-02-05  7:28                 ` Lars Ingebrigtsen
2012-01-29 16:00         ` Christoph Scholtes
2012-01-29 16:47           ` Juanma Barranquero
2012-01-29 17:08             ` Christoph Scholtes
2012-01-29 17:26               ` Juanma Barranquero [this message]
2012-01-30  1:00                 ` Chong Yidong
2012-01-30 12:53                   ` Ted Zlatanov
2012-01-29 17:05           ` Eli Zaretskii
2012-01-30 13:07           ` Ted Zlatanov
2012-01-30 13:18             ` Juanma Barranquero

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='CAAeL0SS+K0pW1KTcoVeVf5j-VnsoexNoY_CxMqBAg9=0yH8bvw@mail.gmail.com' \
    --to=lekktu@gmail.com \
    --cc=cschol2112@googlemail.com \
    --cc=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 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).