Re: Debian readline/libedit breakage

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: Debian readline/libedit breakage
Дата
Msg-id 201102161729.p1GHT9125870@momjian.us
обсуждение исходный текст
Ответ на Re: Debian readline/libedit breakage  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Debian readline/libedit breakage  (Andrew Dunstan <andrew@dunslane.net>)
Re: Debian readline/libedit breakage  ("Joshua D. Drake" <jd@commandprompt.com>)
Список pgsql-hackers
Tom Lane wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
> > On Fri, Feb 11, 2011 at 3:10 PM, Tom Lane <tgl@sss.pgh.pa.us> 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
that.

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  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: contrib loose ends: 9.0 to 9.1 incompatibilities
Следующее
От: Robert Haas
Дата:
Сообщение: Re: Sync Rep for 2011CF1