Often requested feature
Created attachment 265353 [details] 0001-Link-packages-to-freshports-rather-than-cgit.patch
(In reply to Paavo-Einari Kaipila from comment #1) This is a problem. I often get "Server too busy. Please try again later. You should never see this message if you are logged in.". I wouldn't link to such a target.
(In reply to Michael Osipov from comment #2) You don't need an internet connection to find the same information as in cgit, because you have the ports tree in your coputer. Users who this is for, do not and cgit provides absolutely no useful information for them anyway.
+100 from me. This is effectively a duplicate of 2022 bug 267798, which was closed (works as intended), however it's not appropriate for me to close this new report. 267798 also mentioned <https://www.freebsd.org/ports/> (website, not documentation), which was later removed. In the Wayback Machine: <https://web.archive.org/web/20230915210803/https://www.freebsd.org/ports/>
(In reply to Graham Perrin from comment #4) It was closed due to gatekeeping and without an actual reason anyway. Official portal mentioned in that closing message does not exist.
>> This is effectively a duplicate of 2022 bug 267798, which was closed (works as intended) > It was closed due to gatekeeping and without an actual reason anyway. Official portal mentioned in that closing message does not exist. (bugs maintainer hat on) The reason given there was that the project has a system, and freshports is an external system. That's a reason you don't like, it's not gatekeeping. I am closing this as a duplicate of that but because it is an exact duplicate. (bug maintainer hat off) I prefer our current system because it's a fast, available system that lowers the gap between users and developers. *** This bug has been marked as a duplicate of bug 267798 ***
(In reply to Alexander Ziaee from comment #6) How about having a conversation and not just closing the ticket, because Graham posted a link to your, well...comment towards the person who opened the previous one? > available system that lowers the gap between users and developers. People who use cgit do not need links for that. Handbook is advertised as a place for people to start their FreeBSD journey. Makefiles might provide some useful information for you, me and everyone who happens to see this thread. For most people however, they are gibberish. And as I said in the previous message, that portal used as an argument does not exist.
> Makefiles might provide some useful information for you, me and everyone who happens to see this thread. For most people however, they are gibberish. "Makefiles were text files, not magically encoded binaries, because that was the unix ethos; printable, debuggable, understandable stuff" ~Stuart Feldman
50/50 so far. You only closed this because Graham posted a link which you weren't very proud of. This topic deserves a conversation or alternatively, the same faith as most doc tickets and to just stay open forever.
Let's make things professional, not personal. Two FreeBSD Foundation examples. An archaic example (2018): the FreeBSD Quickstart Guide <https://freebsdfoundation.org/wp-content/uploads/2018/11/quickstartguidefinal.pdf> referred to a page that was first published in June 2017. Its current address: <https://freebsdfoundation.org/freebsd-project/resourcesold/installing-a-port-on-freebsd/> – that's somewhat outdated (it pictures, and describes, <https://www.freebsd.org/ports/>, which no longer exists; and so on). A more modern example (2023): the recap of the second Enterprise Working Group Meeting, which used FreshPorts links (not cgit) for projects. <https://freebsdfoundation.org/blog/recap-of-second-enterprise-working-group-meeting/>.