In ports/ there's convention to have unsuffixed package track the latest stable or be a meta port while suffixed packages track any other version or development snapshots. For example, - security/gnupg vs. security/gnupg1 - graphics/glfw vs. graphics/glfw2 or - lang/python vs. lang/pythonXY - lang/gcc vs. lang/gccXY Also new FreeBSD users (former Linux or macOS) may expect "ncdu" to track the latest: Arch, Gentoo, Homebrew, MacPorts, NixPkgs, openmamba, PkgSrc, Solus, T2 SDE use plain "ncdu" for 2.x series according to https://repology.org/project/ncdu/versions (ignore 1.*) vs. Alpine, FreeBSD, Void use "ncdu2" for 2.x series according to https://repology.org/project/ncdu2/versions
If bin/ncdu (unsuffixed) is important consider converting to USES=uniquefiles.
+1, I agree that's what most users would expect
Here's the reasons I'd like to keep ncdu for 1.x. 1. ncdu 1.x is the LTS version. It is not a legacy version. from official site: C version (LTS) 1.19 Lags a bit behind on the 2.x version in terms of features and performance, but is still being maintained and perfectly usable. 2. ncdu 2.x uses zig which brings llvm makes it heavier. And it only sticks to specific zig version. from official site: Note that the Zig language and compiler are still very much unstable. This version of ncdu will only work with the version of the Zig compiler noted above. Use the ncdu 1.x branch if this does not work for you or if you need a more stable compilation environment. 3. ncdu2 may not be the latest version. The reality is you could use the latest feature from ncdu (1.x). Take ncdu 1.19 and ncdu 2.3 for example, both brings the following changes: - Add –(enable|disable)-natsort options - Add indicator to apparent size/disk usage selection in the footer We have 1.19 in the ports tree already. 2.3 is yet to come due to zig.