> It will be impossible to create package for both in official repos until name conflict will be resolved.
Not really, if your package manager allows hierarchies then something like `network.kitty` and `x11.kitty` could be used. If they have to use the same namespace then names like `kitty-ssh` and `kitty-term` could be used.
If you're installing binaries into a single location (e.g. /usr/bin) then they can either be left to conflict, or renamed by the packager (e.g. Debian renames task-spooler's `ts` to `tsp`, to avoid conflicting with moreutils' `ts` timestamp command). If packages are installed to independent locations (e.g. as in Nix and Guix) then there's no need to rename anything, although it might be nice to provide symlinks with unique names so that both can be used from the same $PATH.
Not really, if your package manager allows hierarchies then something like `network.kitty` and `x11.kitty` could be used. If they have to use the same namespace then names like `kitty-ssh` and `kitty-term` could be used.
If you're installing binaries into a single location (e.g. /usr/bin) then they can either be left to conflict, or renamed by the packager (e.g. Debian renames task-spooler's `ts` to `tsp`, to avoid conflicting with moreutils' `ts` timestamp command). If packages are installed to independent locations (e.g. as in Nix and Guix) then there's no need to rename anything, although it might be nice to provide symlinks with unique names so that both can be used from the same $PATH.