|| ||Bruce Momjian <bruce-AT-momjian.us> |
|| ||Tom Lane <tgl-AT-sss.pgh.pa.us> |
|| ||Re: Debian readline/libedit breakage |
|| ||Wed, 16 Feb 2011 12:29:09 -0500 (EST)|
|| ||Robert Haas <robertmhaas-AT-gmail.com>,
Alvaro Herrera <alvherre-AT-commandprompt.com>,
Greg Smith <greg-AT-2ndquadrant.com>, Michael Banck <mbanck-AT-debian.org>,
Andrew Dunstan <andrew-AT-dunslane.net>, jd <jd-AT-commandprompt.com>,
|| ||Article, Thread
Tom Lane wrote:
> Robert Haas <firstname.lastname@example.org> writes:
> > On Fri, Feb 11, 2011 at 3:10 PM, Tom Lane <email@example.com> wrote:
> >> We have code that exists in both psql and the backend (cf src/port/)
> >> so I'm not sure this really will satisfy the more rabid GPL partisans.
> >> And this whole discussion is about satisfying the most rabid of them,
> >> remember. I don't really think that anything other than "relicense all
> >> of Postgres as GPL" will make them happy.
> > Which, by the way, *no one* has the authority to do.
> Right. So the long term solution in my mind is to migrate away from
> readline and towards libedit. I'm just not sufficiently worried about
> this to put any of my own cycles into making libedit good enough.
Agreed. If we can create a database, someone can get libedit to work
100%! There is no excuse for this not being done, seeing that
libreadline has been (viral) GPL forever and has changed APIs regularly
and broken things for us. Even going with GNUTLS does not help us with
Can someone take ownership of this, get involved with the libedit folks,
get Debian to use their fixes, and solve this problem for us?
Bruce Momjian <firstname.lastname@example.org> http://momjian.us
+ It's impossible for everything to be true. +
Sent via pgsql-hackers mailing list (email@example.com)
To make changes to your subscription:
to post comments)