Now package or port ponit to git.freebsd,org in FreeBSD documentation. such as package:korean/ibus-hangul[] will link to https://cgit.freebsd.org/ports/tree/korean/ibus-hangul/pkg-descr. It makes no sense, many people can't read the source code or the port doesn't have a pkg-descr, only a makefile. The link to freshports.org is more helpful for people to find out more about the package.It's inconvenient to change it to git now, so I'm asking to change it back.
*** Bug 267799 has been marked as a duplicate of this bug. ***
An example of context: at <https://www.freebsd.org/ports/>, seeking package name: ibus-hangul – results in <https://www.freebsd.org/cgi/ports.cgi?query=ibus-hangul&stype=name>, with links out to cgit URLs such as these: <https://cgit.freebsd.org/ports/tree/korean/ibus-hangul> <https://cgit.freebsd.org/ports/plain/korean/ibus-hangul/pkg-descr?revision=HEAD> <https://cgit.freebsd.org/ports/log/korean/ibus-hangul> Compare with <https://www.freshports.org/korean/ibus-hangul/>. ---- Documentation that refers to <https://www.freebsd.org/ports/> includes: <https://docs.freebsd.org/en/books/handbook/book/#ports-overview> <https://www.freebsd.org/ports/> does, currently, include a sidebar link to FreshPorts.
Freshports is not an official part of the FreeBSD Project. When the new official FreeBSD application portal is listed we will switch from git to the new portal. I close the ticket, thanks for the suggestion.
The cgit links are actually something people who are successful here love about freebsd. Freebsd has minimal abstractions compared to other operating systems, so it's easier to figure out what's going on and work with the system. The bread and butter of the lasting and contributing community is people that rely on this type of design. I hope the new application portal will be simple like cgit and not create excessive complexity by trying to make abstractions for user friendliness. Freebsd is the best stick shift on the market. It's a lot better for the ecosystem to just teach people how to drive.
Contexts: - <https://discord.com/channels/727023752348434432/757543661058654269/1325715356966322196> (Monday 2025-01-06) in the #community channel; I'll make the suggested PR in GitHub - tracking bug 283881