| |||||||||||||
PostgreSQL, OpenSSL, and the GPLPostgreSQL, OpenSSL, and the GPLPosted Feb 16, 2011 20:43 UTC (Wed) by obrakmann (subscriber, #38108)In reply to: PostgreSQL, OpenSSL, and the GPL by dberkholz Parent article: PostgreSQL, OpenSSL, and the GPL
I think so... It's mind-boggling, really, if it's true.
Especially since Debian seems to use a libedit from 2008 (according to the package version at least: 2.11-20080614-2), while the latest changelog entry from 2010 (on the homepage linked to from this article) says "Now with UTF-8 support"
Lovely.
(Log in to post comments)
PostgreSQL, OpenSSL, and the GPL Posted Feb 16, 2011 20:50 UTC (Wed) by mbanck (subscriber, #9035) [Link]
People tried the latest libedit version with psql and it was still (differently) broken.
PostgreSQL, OpenSSL, and the GPL Posted Feb 16, 2011 22:27 UTC (Wed) by mikov (subscriber, #33179) [Link]
It seems to me that fixing libedit, or even rewriting it from scratch should be much easier than replacing OpenSSL. I mean, editing a single line of text is a problem? Really? Can someone explain why?
PostgreSQL, OpenSSL, and the GPL Posted Feb 17, 2011 5:06 UTC (Thu) by khim (subscriber, #9252) [Link] I mean, editing a single line of text is a problem? Really? Can someone explain why? Sure. It's easy: because this book weights over five pounds (2kg)... Editing of a single line of US-ASCII text is easy and libedit does it acceptably well. But when you go beyond that... some characters take two positions on screen, some don't take anything at all, etc. Readline does not do it all that well, but in comparison to libedit... well, it's not so simple to edit a single line of text, believe me...
|
|||||||||||||