The OpenNET Project / Index page

[ новости /+++ | форум | теги | ]

Поиск:  Каталог документации / Документация по FreeBSD / Руководства по FreeBSD на английском

2.6 Submitting the port

First, make sure you have read the DOs and DON'Ts section.

Now that you are 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 your work directory or the pkgname.tgz package, so delete them now. Next, simply include the output of shar `find port_dir` in a bug report and send it with the send-pr(1) program (see Bug Reports and General Commentary for more information about send-pr(1)). If the uncompressed port is larger than 20KB, you should compress it into a tarfile and use uuencode(1) before including it in the bug report (uuencoded tarfiles are acceptable even if the bug report is smaller than 20KB but are not preferred). Be sure to classify the bug report as category ports and class change-request (Do not mark the report confidential!). Also add a short description of the program you ported to the ``Description'' field of the PR and the shar or uuencoded tarfile to the ``Fix'' field. The latter one helps the committers a lot, who use scripts for the ports-work.

One more time, do not include the original source distfile, the work directory, or the package you built with make package.

Note: In the past, we asked you to upload new port submissions in our FTP site ( This is no longer recommended as read access is turned off on the incoming/ directory of that site due to the large amount of pirated software showing up there.

After you have submitted your port, please be patient. Sometimes it can take a few months before a port is included in FreeBSD, although it might only take a few days. You can view the list of ports waiting to be committed to FreeBSD.

Once we have looked at your port, we will get back to you if necessary, and put it in the tree. Your name will also appear in the list of ``Additional FreeBSD contributors'' in the FreeBSD Handbook and other files. Isn't that great?!? :-)

Note: You can make our work a lot easier, if you use a good description in the synopsis of the problem report. We prefer something like ``New port: <short description of the port>'' for new ports and ``Update port: <category>/<port> <short description of the update>'' for port updates. If you stick to this scheme, the chance that one takes a look at your PR soon is much bigger.

For questions about the FreeBSD ports system, e-mail <>.
For questions about this documentation, e-mail <>.

Inferno Solutions
Hosting by

Закладки на сайте
Проследить за страницей
Created 1996-2024 by Maxim Chirkov
Добавить, Поддержать, Вебмастеру