[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#1013246: RFS: kmscon/9.0.0-1 [ITP] -- Simple terminal emulator based on Kernel Mode Setting



Op 20-06-2022 om 12:09 schreef Thomas Dickey:
On Mon, Jun 20, 2022 at 12:52:20AM +0200, Adam Borowski wrote:
On Sun, Jun 19, 2022 at 11:02:54PM +0200, Victor Westerhuis wrote:
  * Package name    : kmscon
    Version         : 9.0.0-1

  kmscon (9.0.0-1) unstable; urgency=medium
  .
    * Initial release (Closes: #1004919)

Hi!
I've uploaded to NEW, as the basic packaging looks good in general.

Integration with Debian conventions, though, requires some work.

The biggest problem: there's only a .service file but no init script,
making kmscon work only with systemd but not with any other init/rc
system.

It fails to set term settings, making cooked mode not work until something

The TSM developer says in the README:

   This library is very similar to libvte of the gnome project. However, libvte is
   highly bound to GTK+, which makes it unsuitable for non-graphics projects that
   need to parse escape sequences. Instead, TSM tries to restrict its API to
   terminal emulation only. Furthermore, TSM does not try to establish a new
   terminal emulation standard, but instead keeps compatibility as close to xterm
   as possible. This is why the TERM variable can be set to xterm-color256 with any
   TSM based terminal emulator.

(because the terminal behavior doesn't come close to xterm, that's
going to produce bug reports)
This text from the README is also included in the description of the binary packages from src:libtsm.

Do you think that the text needs to be changed for a next upload? Or should I add a warning message?

else (eg. bash) messes with them.  This makes eg. backspace not work on
the login prompt.

It probably should run getty instead of inventing its own stuff.

/etc/issue should be printed before the login prompt.


There's also a bunch of upstreamish issues, such as application keypad mode
not working, or failing to either support existing mouse daemons (such as
consolation) or providing its own mouse handling, but such stuff seems more
fit for the upstream bug tracker.

The libtsm upstream bug tracker doesn't show much recent activity
(and glancing over the libtsm source, can readily see that there are
a lot of problems yet to be reported - perhaps this package will do that).

To start with, it's not "VT100 compatible".

The upstream maintainer of the packaged libtsm fork is the same as the upstream maintainer for kmscon and they've been very responsive when issues came up while packaging kmscon and libtsm.

I will work with them to improve the quality for future releases.
--
Victor Westerhuis


Reply to: