https://bugzilla.redhat.com/show_bug.cgi?id=1686506 --- Comment #8 from Jason A. Donenfeld <Jason@xxxxxxxxx> --- It's unfortunate you had that misguided discussion without the input of upstream. I disagree with the conclusion there of WireGuard being merely, "a piece of software, which just happens to require a kernel module in order to operate." We rather expect that many different types of software will be formed from the small basic building block of a WireGuard tunnel. The name of the tools is wireguard-tools. As soon as WireGuard is upstreamed, the name of the repo will be wireguard-tools. The tarballs of that software will be called wireguard-tools-1.0.tar.xz. Extremely common nomenclature for tools that operate particular network interface types is -tools. So I urge you to both stick with the naming conventions used by both numerous upstream kernel networking projects and by the WireGuard project itself. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx
