Hi,

I maintain the package **ssh-tools**
and upstream as well.
These are a mix of Bash and Perl scripts.

Recently I do more stuff with Go
and have new tools written in Go
and don't want to mix them with the Bash and Perl Scripts
because that would be difficult to package (also for other Distros and OSes).

I am not sure how to name the new tools upstream repo
and therefore the package name.

Currently it's ssh-toolz (with a "z")
since I found examples like **python3-toolz**.
But I also thought about ssh-tools2 sind there is **wget2**.

Any suggestion what the best practice is to name similar packages?

Reply via email to