On Tue, Dec  1, 2015 at 03:35:39PM -0500, Robert Haas wrote:
> > Well, you'd have to use MacPorts' version of the openssl libraries,
> > too, since there'd be no certainty that their headers match the
> > Apple-provided libraries (in fact, I'd bet a lot that they don't).
> > This would be a pain if you wanted to put your compiled PG executables
> > on some other Mac.
> Yeah, I guess it means that people building for MacOS X will probably
> have to ship OpenSSL as a dependency, which also means that they will
> need to update it when new versions are released.  That is already a
> pretty obnoxious disease on Windows, and it's unfortunate to see it
> spreading.  It would save us a good deal of staff time here at
> EnterpriseDB if we didn't have to do new releases of everything on
> Windows every time there is an OpenSSL update.

Do we still have licensing issues if we ship Postgres and OpenSSL

  Bruce Momjian  <br...@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+ Roman grave inscription                             +

Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to