Date: Sat, 17 Apr 2021 21:27:38 GMT From: "Danilo G. Baio" <dbaio@FreeBSD.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org Subject: git: 2644b2cda8 - main - articles/contributing: Update ports resources Message-ID: <202104172127.13HLRcA9027381@gitrepo.freebsd.org>
next in thread | raw e-mail | index | archive | help
The branch main has been updated by dbaio (ports committer): URL: https://cgit.FreeBSD.org/doc/commit/?id=2644b2cda8a74ef2cc235bfc202a66e72458b211 commit 2644b2cda8a74ef2cc235bfc202a66e72458b211 Author: Danilo G. Baio <dbaio@FreeBSD.org> AuthorDate: 2021-04-17 21:20:47 +0000 Commit: Danilo G. Baio <dbaio@FreeBSD.org> CommitDate: 2021-04-17 21:25:45 +0000 articles/contributing: Update ports resources Add a note that portsmon is currently not working, more visibility to portscout and add new resource portsfallout. Approved by: debdrup (doc) Differential Revision: https://reviews.freebsd.org/D29715 --- .../content/en/articles/contributing/_index.adoc | 25 +++++++++++++++++++--- 1 file changed, 22 insertions(+), 3 deletions(-) diff --git a/documentation/content/en/articles/contributing/_index.adoc b/documentation/content/en/articles/contributing/_index.adoc index 16d4c1cf1a..208b019e6b 100644 --- a/documentation/content/en/articles/contributing/_index.adoc +++ b/documentation/content/en/articles/contributing/_index.adoc @@ -247,6 +247,10 @@ It is a good idea to start with adopting a port that you use regularly. Unmaintained ports have their `MAINTAINER` set to `ports@FreeBSD.org`. A list of unmaintained ports and their current errors and problem reports can be seen at the http://portsmon.FreeBSD.org/portsconcordanceformaintainer.py?maintainer=ports%40FreeBSD.org[FreeBSD Ports Monitoring System]. +On https://portsfallout.com/fallout?port=&maintainer=ports%40FreeBSD.org[PortsFallout] can be seen a list of unmaintained ports with errors. + +Many unmaintained ports can have pending updates, this can be seen at the https://portscout.freebsd.org/ports@freebsd.org.html[FreeBSD Ports distfile scanner]. + Some ports affect a large number of others due to dependencies and slave port relationships. Generally, we want people to have some experience before they maintain such ports. @@ -254,6 +258,11 @@ You can find out whether or not a port has dependencies or slave ports by lookin (The name of the file varies by release of FreeBSD; for instance, [.filename]#INDEX-8#.) Some ports have conditional dependencies that are not included in a default [.filename]#INDEX# build. We expect you to be able to recognize such ports by looking through other ports' [.filename]#Makefile#'s. +[NOTE] +====== +The FreeBSD Ports Monitoring System (portsmon) is currently not working due to latest Python updates. +====== + ==== How to adopt the port First make sure you understand your <<maintain-port>>. @@ -490,19 +499,27 @@ If you can make them feel that their contribution is appreciated (and it should [[fix-broken]] === Finding and fixing a broken port -There are two really good places to find a port that needs some attention. +There are some really good places to find a port that needs some attention. You can use the https://bugs.freebsd.org/search[web interface] to the Problem Report database to search through and view unresolved PRs. The majority of ports PRs are updates, but with a little searching and skimming over synopses you should be able to find something interesting to work on (the `sw-bug` class is a good place to start). The other place is the http://portsmon.FreeBSD.org/[FreeBSD Ports Monitoring System]. In particular look for unmaintained ports with build errors and ports that are marked `BROKEN`. + +https://portsfallout.com/[PortsFallout] shows port issues gathered from the FreeBSD package building. + It is OK to send changes for a maintained port as well, but remember to ask the maintainer in case they are already working on the problem. Once you have found a bug or problem, collect information, investigate and fix! If there is an existing PR, follow up to that. Otherwise create a new PR. Your changes will be reviewed and, if everything checks out, committed. +[NOTE] +====== +The FreeBSD Ports Monitoring System (portsmon) is currently not working due to latest Python updates. +====== + [[mortal-coil]] === When to call it quits @@ -525,11 +542,11 @@ In 2005 more than eleven thousand ports PRs were submitted! Following this artic The https://bugs.freebsd.org/bugzilla/query.cgi[Problem Report database]. -The http://portsmon.FreeBSD.org/[FreeBSD Ports Monitoring System] can show you cross-referenced information about ports such as build errors and problem reports. +The http://portsmon.FreeBSD.org/[FreeBSD Ports Monitoring System (portsmon)] can show you cross-referenced information about ports such as build errors and problem reports. If you are a maintainer you can use it to check on the build status of your ports. As a contributor you can use it to find broken and unmaintained ports that need to be fixed. -The http://portscout.FreeBSD.org[FreeBSD Ports distfile scanner] can show you ports for which the distfiles are not fetchable. +The http://portscout.FreeBSD.org[FreeBSD Ports distfile scanner (portscout)] can show you ports for which the distfiles are not fetchable. You can check on your own ports or use it to find ports that need their `MASTER_SITES` updated. package:ports-mgmt/poudriere[] is the most thorough way to test a port through the entire cycle of installation, packaging, and deinstallation. @@ -544,6 +561,8 @@ It is a good place to ask for help. You can https://lists.freebsd.org/mailman/listinfo[subscribe, or read and search the list archives]. Reading the archives of the {freebsd-ports-bugs} and the {svn-ports-head} may also be of interest. +https://portsfallout.com/[PortsFallout] is a place to help in searching for the https://lists.freebsd.org/pipermail/freebsd-pkg-fallout/[FreeBSD package-fallout archive]. + [[ideas-contributing]] == Getting Started in Other Areas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202104172127.13HLRcA9027381>