|
From: | Michael Petch |
Subject: | Re: [Bug-gnubg] Serious bug: Random.org - Important Request for Comments |
Date: | Tue, 13 Jan 2015 13:21:56 -0700 |
User-agent: | Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 |
On 2015-01-13 1:11 PM, Dan Fandrich wrote: > An end > user compiling his own gnubg doesn't even need to concern himself with the > license of the SSL library (as long as he doesn't redistribute the code) while > packagers can choose one of a number of SSL back-ends compatible with > distribution. Please read what I said " It primarily has to do with RELEASING BINARIES that use OpenSSL for TLS on the back end when linked with GPL code" The problem is that GNUbg does official binary builds for Windows and OS/X. So this issue directly impacts our production of binaries. I am well aware that the issue isn't one that concerns those who build from source themselves. The MingW environment I use doesn't even have GnuTLS as a package. So I happened to build Nettle (and had libgmp installed) and wouldn't you know it the GNUtls build fails (and apparently I'm not alone with that issue) So I'll have to find a back end that actually will work under MingW. It just so happens that OpenSSL just works on Msys/Mingw which is why it would have been convenient. As for Macports which we use on OS/X I have already confirmed that one can build a gnutls variant. -- Michael Petch GNU Backgammon Maintainer / Developer OpenPGP FingerPrint=D81C 6A0D 987E 7DA5 3219 6715 466A 2ACE 5CAE 3304
[Prev in Thread] | Current Thread | [Next in Thread] |