[MacPorts] #52866: sqlite3: unable to enter non-ASCII characters

[MacPorts]

#52866: sqlite3: unable to enter non-ASCII characters
--------------------+---------------------
 Reporter:  raimue  |      Owner:  mww@…
     Type:  defect  |     Status:  new
 Priority:  Normal  |  Milestone:
Component:  ports   |    Version:
 Keywords:          |       Port:  sqlite3
--------------------+---------------------
 The sqlite3 shell does not allow typing non-ASCII characters. To reproduce
 this, open sqlite3 and try to copy and paste "Müller" into a query. The
 umlaut will be skipped and you end up with "Mller".

 This works correctly with /usr/bin/sqlite3 on macOS 10.12.1, so it is
 probably not an upstream problem, but in the packaging.

 {{{
 $ otool -L /opt/local/bin/sqlite3
 /opt/local/bin/sqlite3:
         /opt/local/lib/libedit.0.dylib (compatibility version 1.0.0,
 current version 1.54.0)
         /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
 version 1238.0.0)
 $ otool -L /usr/bin/sqlite3
 /usr/bin/sqlite3:
         /usr/lib/libncurses.5.4.dylib (compatibility version 5.4.0,
 current version 5.4.0)
         /usr/lib/libsqlite3.dylib (compatibility version 9.0.0, current
 version 252.0.0)
         /usr/lib/libedit.3.dylib (compatibility version 2.0.0, current
 version 3.0.0)
         /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
 version 1238.0.0)
 }}}

 Maybe it is the missing ncurses, which is in `depends_lib`, but not
 actually linked. Could also be a problem with `--enable-readline` vs.
 `--enable-editline`. The configure script states that the supported
 library is auto-detected, so one of them should be passed as
 `--disable-*line`.

--
Ticket URL: <https://trac.macports.org/ticket/52866>
MacPorts <https://www.macports.org/>
Ports system for macOS