Package: wnpp Severity: wishlist Owner: Su Kang Yin <[email protected]> X-Debbugs-Cc: [email protected], [email protected]
* Package name : rust-xcomm (binary packages: xcomm, librust-xcomm-dev) Version : 0.1.2 Upstream Contact: Su Kang Yin <[email protected]> * URL : https://github.com/cantona/xcomm * License : MIT or Apache-2.0 Programming Lang: Rust Description : serial console with a control socket for scripts xcomm is a serial terminal with minicom's common options and its Ctrl-A command keys (help, quit, break, DTR/RTS, baud rate, capture, zmodem send and receive). Unless disabled, each session has a control socket, so another program (a script, a test or a coding agent) can send commands, wait for prompts, read output, change line settings and run zmodem transfers on the console the user is watching. It reopens the port when a USB adapter is unplugged and plugged back in, and takes UUCP locks compatible with minicom (and flocks the device as picocom does). Why: embedded developers increasingly drive board consoles from scripts and coding agents. minicom and picocom have no way for another process to use a running session; tio can redirect its I/O to a socket, but xcomm's control socket is request/response: waits on regexes with offsets and exit codes, run-until-prompt, ordered break, DTR/RTS and line changes, zmodem transfers, and an agent skill describing it. xcomm is a clean-room implementation (not derived from minicom). All its Rust dependencies are in Debian unstable at the versions it needs (lexopt, memchr, libc, rustix, serde, serde_json, regex, and toml for the tests). The program's code is the crate's library target (its binaries are thin wrappers over it), so debcargo also builds librust-xcomm-dev; nothing outside xcomm is expected to depend on it. I plan to maintain it within the Debian Rust team (debcargo-conf) and am looking for a sponsor; I am its upstream author.

