Contributing to the FreeBSD Ports Collection
Prev |  |

# 8 Resources for ports maintainers and contributors

The Porter's Handbook is your hitchhiker's guide to the ports system. Keep it handy!

Writing FreeBSD Problem Reports describes how to best formulate and submit a PR. In 2005 more than eleven thousand ports PRs were submitted! Following this article will greatly assist us in reducing the time needed to handle your PRs.

The Problem Report database.

Pointyhat is the ports build cluster. You can use Pointyhat to check port build logs across all architectures and major releases.

The FreeBSD Ports Monitoring System 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 FreeBSD Ports distfile scanner 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.

The ports tinderbox is the most thorough way to test a port through the entire cycle of installation, packaging, and deinstallation. It features a command-line interface but also can be controlled via a web interface. Please see `ports/ports-mgmt/tinderbox`. More documentation is located at the marcuscom tinderbox home page.

portlint(1) is an application which can be used to verify that your port conforms to many important stylistic and functional guidelines. portlint is a simple heuristic application, so you should use it only as a guide. If portlint suggests changes which seem unreasonable, consult the Porter's Handbook or ask for advice.

The FreeBSD ports mailing list is for general ports-related discussion. It is a good place to ask for help. You can subscribe, or read and search the list archives. Reading the archives of the FreeBSD ports bugs mailing list and the FreeBSD CVS ports commit list may also be of interest.

Prev | Home |
When to call it quits |  |