Re: Debian readline/libedit breakage

From: Daniel Farina <drfarina(at)acm(dot)org>
To: jd(at)commandprompt(dot)com
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Debian readline/libedit breakage
Date: 2011-02-10 22:52:54
Message-ID: AANLkTik--1rdSK2nevhmWu9MQxn49CwQ0W-sPqtOkHm9@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 10, 2011 at 2:34 PM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
> Hello,
>
> Per:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607109
>
> It seems we may have a problem to consider. As far as I know, we are the
> only major platform that supports libedit but our default is readline.
> Unfortunately readline is not compatible with OpenSSL (apparently?)
> licensing.
>
> This seems that it may be a problem for us considering the pre-package
> builds we do.
>
> What does everyone think? Should we work on getting libedit up to snuff?

I have to admit, this change in debian packaging -- which I have
noticed, and not a little -- makes my hands angry. I considered
looking into the problem, but were I doing it, I would have considered
teaching psql to support NSS or GnuTLS as totally viable alternatives
to this problem, as to keep readline.

--
fdr

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2011-02-10 22:55:55 Re: Debian readline/libedit breakage
Previous Message Tom Lane 2011-02-10 22:45:23 Re: SPI_exec doesn't return proc context (on 9.1)