Date: Thu, 22 Oct 2015 21:35:15 -0400
From: Stephen Frost <sfrost@snowman.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: David Fetter <david@fetter.org>, Robert Haas <robertmhaas@gmail.com>,
 Thomas Munro <thomas.munro@enterprisedb.com>,
 Jeff Janes <jeff.janes@gmail.com>,
 Alvaro Herrera <alvherre@2ndquadrant.com>,
 Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Making tab-complete.c easier to maintain
Message-ID: <20151023013515.GH3685@tamriel.snowman.net>
References: 
 <CAEepm=1=Hdt9TCM3BRiVE6NCnXHyDDki+YVPhfZ02_=niU=8cA@mail.gmail.com>
 <CAMkU=1yt=Ed7+K4sUisdUkt-wDhGnxdkDqs_43uJvhJYFA56gQ@mail.gmail.com>
 <CAEepm=1ns0rbo+xun_j6_PwDT6zmEPuNggy=Vaie-3peF2C44Q@mail.gmail.com>
 <CAEepm=2X08QRoJD3Bu4em-w=c=Q7SCCHM404jK-ercR4H1xtkw@mail.gmail.com>
 <CA+TgmoYow9qMFJ8hJipmd7K9=_xeUtAVVarQJGY401_nTnopeQ@mail.gmail.com>
 <51382.1445549813@sss.pgh.pa.us>
 <20151022221425.GB22539@fetter.org>
 <53412.1445555106@sss.pgh.pa.us>
 <20151022232610.GC22539@fetter.org>
 <54565.1445558534@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature"; boundary="5RwbhZS+X6AYo9/K"
Content-Disposition: inline
In-Reply-To: <54565.1445558534@sss.pgh.pa.us>
User-Agent: Mutt/1.5.21 (2010-09-15)
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org


--5RwbhZS+X6AYo9/K
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Tom Lane (tgl@sss.pgh.pa.us) wrote:
> David Fetter <david@fetter.org> writes:
> > On Thu, Oct 22, 2015 at 04:05:06PM -0700, Tom Lane wrote:
> >> Given the license issues around GNU readline, requiring it seems like
> >> probably a non-starter.
>=20
> > I should have made this more clear.  I am not an IP attorney and don't
> > play one on TV, but this is what I've gotten out of conversations with
> > IP attorneys on this subject:
>=20
> I'm not an IP attorney either, and the ones I've talked to seem to agree
> with you.  (Red Hat's corporate attorneys, at least, certainly thought
> that when I last asked them.)  But the observed facts are that some
> distros refuse to ship psql-linked-to-readline, and substitute libedit
> instead, because they got different advice from their attorneys.

The issue for Debian, at least, isn't really about libreadline or
libedit, it's about the GPL and the OpenSSL license.  From the Debian
perspective, if we were able to build with GNUTLS or another SSL library
other than OpenSSL (which I know we've made some progress on, thanks
Heikki...) then Debian wouldn't have any problem shipping PG linked with
libreadline.

> If we desupport libedit, the end result is going to be these distros
> shipping psql with no command-line-editing support at all.  Our opinion,
> or even our lawyers' opinion, is unlikely to prevent that outcome.
>=20
> While libedit certainly has got its bugs and deficiencies, it's way better
> than nothing at all, so I think we'd better keep supporting it.

I agree that it's probably not a good idea to desupport libedit.
However, I don't believe supporting libedit necessairly prevents us
=66rom providing better support when libreadline is available.
Debian-based distributions won't be able to reap the benefits of that
better support until we remove the OpenSSL dependency, which is
unfortunate, but other distributions would be able to.

Also, if the PG project is agreeable to it, there's no reason why we
couldn't provide full libreadline-enabled builds off of
apt.postgresql.org, regardless of what Debian wants.  That would add a
bit of extra burden on our package maintainers, as there isn't any
difference between packages built for Debian and packages built for
apt.p.o currently, I don't believe, but it seems like it'd be a pretty
minor change that would be well worth it if we get better libreadline
integration.

The one bit of all of this that worries me is that we would take
libreadline for granted and the libedit support would end up broken.
That seems a relatively minor concern though, as it sounds like there is
a fair bit of exercise of the libedit path due to the commercial forks
of PG which make use of it to avoid the GPL.

Thanks!

Stephen

--5RwbhZS+X6AYo9/K
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJWKY7TAAoJEO1sijiDR2RVTZsQAKzcJILnO9Cnm2UJ3s4pJrWH
HbyzXts9YylzTJyyZL3nnmOe7+QFOQWPXhTYumpZAwaXvKcLovJuAdL+rvAEUZUm
j72u5es+PL3YzVGkyVh9VRbWa6V6CCq2malZEi10cjTaC8eVyaesJKfRm0tdH9cI
cduRf1Qh32kxmyyBRLw9a/ZZ6BZGGasZHMVFgHzc6pPNb/57Z7MUEo1qdeBVl4yv
pRMqUUeNixfeQ0GB5KQKC51MHWz7rQZorxjyypJnRdKLOrNSTi4NkWankwLIWBXD
rBoOcSt5Sv8Zg/7iwJ9I1SjqUvT5VqPlHsEcAVC7M7V0/Yc5UCdMVewj6X1UXU55
Ckqzqduo2sSiUCvmrtlpkm78GzjP11Zx0G8Blu93Hm2F/zUe0PZMeNxbycOytxxc
n9AMhYqDBP0V7MgQ0cTYIECR05plcnTS2eDlytuQQkfm8xHtNypjMpjMzuN8uMJ4
f5/Pr1a1biLxitjYoBCfbbGLBLZUpafi37QWYTTHhVn7x3r62OO1Q9yyy/fq6Unv
3KdN5qU0yvczterIuj3rPgkAuoeMnn8Fn9aKap+B3STH5/Hl6KwhqVWkxDUlM8cF
tBEB9uKVF/QxuQIouUOXKJEvi6ZyDPVyGOPqSnMq+Xg82/BGFlwXsjVeBGg0IqDE
6oLrLhUQbH/g4BnGY0fZ
=yQkQ
-----END PGP SIGNATURE-----

--5RwbhZS+X6AYo9/K--