diff --git a/en_US.ISO8859-1/books/porters-handbook/book.xml b/en_US.ISO8859-1/books/porters-handbook/book.xml index 0e201624dc..c4947fa72f 100644 --- a/en_US.ISO8859-1/books/porters-handbook/book.xml +++ b/en_US.ISO8859-1/books/porters-handbook/book.xml @@ -447,43 +447,43 @@ PLIST_DIRS= lib/X11/oneko Submitting the New Port - Before you submit the new port, make sure you have read + Before submitting the new port, read the DOs and DON'Ts section. - Now that you are happy with your port, the only thing + Once happy with your port, the only thing remaining is to put it in the main &os; ports tree and make - everybody else happy about it too. We do not need your + everybody else happy about it too. We do not need the work directory or the - pkgname.tgz package, so delete them now. - Next, assuming your port is called oneko, + pkgname.tgz package, so delete them now. + Next, build the &man.shar.1; file. Assuming the port is called oneko, cd to the directory above where the - oneko directory is located, and then type - the following: + oneko directory is located, and then type: shar `find oneko` > oneko.shar - Include your oneko.shar file in a bug - report and send it with the &man.send-pr.1; program (see + Include oneko.shar in a bug + report and send it with &man.send-pr.1;. See Bug Reports and General Commentary for more information - about &man.send-pr.1;). 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 (e.g., perhaps a + about &man.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. + the .shar file to the Fix field. - You can make our work a lot easier, if you use a good - description in the synopsis of the problem report. We + 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. If you stick to this - scheme, the chance that someone will take a look at your PR - soon is much better. + 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 @@ -492,14 +492,13 @@ PLIST_DIRS= lib/X11/oneko make package; and, do use &man.shar.1; for new ports, not &man.diff.1;. - After you have submitted your port, please be patient. - Sometimes it can take a few months before a port is included - in &os;, although it might only take a few days. You can - view the list of ports - PRs waiting to be committed to &os;. + After submitting the port, please be patient. The time needed + to include a new port in &os; can vary from a few days to a + a few months. The list + of pending port PRs can be viewed at . - Once we have looked at your port, we will get back to you + 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