(improved) Debian package in preparation, command name collision concern
Hi, Thanks for interesting software.
Being a user of QMK and home position MOD keys, this is interesting tool to be on my Linux host machine so I can have similar experience with my laptop itself without my external 4x14 ortholinear keyboard.
Anyway, I made some improvements on #38 (closed) packaging effort. Now package should be acceptable shape for Debian. (No more package test failure for piuparts repeat install test).
(This now has manpages, so Debian folks will not complain.)
But before uploading, I would like to ask if you want to keep generic name command or not.
While thinking about packaging this for Debian, I realize some concern. Debian already has "bear" package which has "intercept" command in bear package which seems mildly popular and generates compilation database for Clang tooling.
So, most likely, this "intercept" command needs to be renamed to make this package as a part of Debian archive.
Generic words for special purpose commands are OK for local commands but for programs to be used in many environments, avoiding name collision early in program distribution is a good idea.
Although I don't see outstanding issue with "mux", this is too short name to be used too Have you thought about renaming all the command in this package consistently? For example, rename bin names as:
intercept -> evdev-intercept
udevmon -> evdev-udevmon
uinput -> evdev-uinput
mux -> evdev-mux
(Git repository name "linux" is a bit confusing but this has practically no negative impact since Debian packager can pick any name for source tree or its tarball name.)
Even if you don't feel like renaming, that's not going to block packaging this. There is always some ways to contain problem. But having clean set of names make it look good. Regards,
Osamu PS: reposting as public issue.