Package: socket-activate Version: 0.1-2 Severity: important Dear Maintainer,
socket-activate is too generic name of the package and the binary it ships. In Debian, we have or had other alternative implementations of the same functionality. Shipped either stand alone, or as part of other packages. For exmaple systemd-socket-activate upstart-socket-bridge and others. Using generic name socket-activate, which is a different implementation to the other utilities and without argument compatibility with them is ill-advised. Please consider renaming the package and the binary to something that is more unique. For example, python-socket-activate or some such. Or maybe even call it heavy-standalone-socket-activate?! Socket activate wrappers are typically used to reduce resources, such that at idle it is desired for socket activation wrapper to use as little resources as possible. That is the case with systemd/upstart/launchd/xinitd/etc. Loading a full blown python3 interpreter does not seem appropriate per each socket and daemon. Have you considered implementing this in something more optimized? for example pypy, cpy, rust, C? Or at least allow socket-activate to listen on many sockets and launch correspending daemon for each? -- System Information: Debian Release: bullseye/sid APT prefers groovy APT policy: (500, 'groovy'), (500, 'focal-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-33-generic (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
