3.6. Submitting the New Port

Before submitting the new port, read the DOs and DON'Ts section.

Once happy with your port, the only thing remaining is to put it in the main FreeBSD ports tree and make everybody else happy about it too. We do not need the work directory or the pkgname.tgz package, so delete them now.

Next, build the shar(1) file. Assuming the port is called oneko, cd to the directory above where the oneko directory is located, and then type: shar `find oneko` > oneko.shar

Include oneko.shar in a bug report and send it with send-pr(1). See Bug Reports and General Commentary for more information about send-pr(1).

Classify the bug report as Category ports and Class change-request. Do not mark the report confidential! Add a short description of the program to the Description field of the PR (perhaps a short version of the COMMENT), and add the .shar file to the Fix field.


Giving a good description in the synopsis of the problem report makes the work of port committers a lot easier. We prefer something like New port: <category>/<portname> <short description of the port> for new ports. Using this scheme makes it easier and faster to begin the work of committing the new port.

One more time, do not include the original source distfile, the work directory, or the package you built with make package; and, do use shar(1) for new ports, not diff(1).

After submitting the port, please be patient. The time needed to include a new port in FreeBSD can vary from a few days to a few months. The list of pending port PRs can be viewed at http://www.FreeBSD.org/cgi/query-pr-summary.cgi?category=ports.

After looking at the new port, we will reply if necessary, and put it in the tree. Your name will also be added to the list of Additional FreeBSD Contributors and other files.

All FreeBSD documents are available for download at http://ftp.FreeBSD.org/pub/FreeBSD/doc/

Questions that are not answered by the documentation may be sent to <freebsd-questions@FreeBSD.org>.
Send questions about this document to <freebsd-doc@FreeBSD.org>.