No more libedit?! - openssl plans to switch to APL2

Started by Andres Freundover 10 years ago6 messages
#1Andres Freund
andres@anarazel.de

Hi,

According to https://www.openssl.org/blog/blog/2015/08/01/cla/ openssl
is planning to relicense to the apache license 2.0. While APL2 is not
compatible with GLP2 it *is* compatible with GPL3.

Greetings,

Andres Freund

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

#2Robert Haas
robertmhaas@gmail.com
In reply to: Andres Freund (#1)
Re: No more libedit?! - openssl plans to switch to APL2

On Sat, Aug 1, 2015 at 11:14 AM, Andres Freund <andres@anarazel.de> wrote:

According to https://www.openssl.org/blog/blog/2015/08/01/cla/ openssl
is planning to relicense to the apache license 2.0. While APL2 is not
compatible with GLP2 it *is* compatible with GPL3.

What's the connection to libedit?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

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

#3Andres Freund
andres@anarazel.de
In reply to: Robert Haas (#2)
Re: No more libedit?! - openssl plans to switch to APL2

On 2015-08-02 12:34:43 -0400, Robert Haas wrote:

On Sat, Aug 1, 2015 at 11:14 AM, Andres Freund <andres@anarazel.de> wrote:

According to https://www.openssl.org/blog/blog/2015/08/01/cla/ openssl
is planning to relicense to the apache license 2.0. While APL2 is not
compatible with GLP2 it *is* compatible with GPL3.

What's the connection to libedit?

Some platforms have to use libedit because linking to both libreadline
and openssl is of debated legality. GPL prohibits additional
restrictions and openssl's license has an advertising clause which is
often interpreted violating the additional-restrictions clause.

Andres

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

#4Andres Freund
andres@anarazel.de
In reply to: Andres Freund (#1)
Re: No more libedit?! - openssl plans to switch to APL2

On 2015-08-01 17:14:10 +0200, Andres Freund wrote:

According to https://www.openssl.org/blog/blog/2015/08/01/cla/ openssl
is planning to relicense to the apache license 2.0. While APL2 is not
compatible with GLP2 it *is* compatible with GPL3.

Just 5 minutes later, some progress on that front:

https://www.openssl.org/blog/blog/2017/03/20/license/

- Andres

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

#5Andreas Karlsson
andreas@proxel.se
In reply to: Andres Freund (#1)
Re: No more libedit?! - openssl plans to switch to APL2

On 08/01/2015 05:14 PM, Andres Freund wrote:

According to https://www.openssl.org/blog/blog/2015/08/01/cla/ openssl
is planning to relicense to the apache license 2.0. While APL2 is not
compatible with GLP2 it *is* compatible with GPL3.

Great! This means that the Debian packages will eventually be able to
drop their LD_PRELOAD hack, which never worked perfectly due to
compiling against libedit or libreadline header resulting in different
binaries.

Andreas

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

#6Andres Freund
andres@anarazel.de
In reply to: Andreas Karlsson (#5)
Re: No more libedit?! - openssl plans to switch to APL2

On 2017-03-24 02:31:47 +0100, Andreas Karlsson wrote:

On 08/01/2015 05:14 PM, Andres Freund wrote:

According to https://www.openssl.org/blog/blog/2015/08/01/cla/ openssl
is planning to relicense to the apache license 2.0. While APL2 is not
compatible with GLP2 it *is* compatible with GPL3.

Great! This means that the Debian packages will eventually be able to drop
their LD_PRELOAD hack, which never worked perfectly due to compiling against
libedit or libreadline header resulting in different binaries.

Well, relicensing is hard. It's far from guaranteed to succeed...

Greetings,

Andres Freund

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