Source string Read only

(itstool) path: sect1/para
461/4610
Context English State
Next, create a <citerefentry><refentrytitle>patch</refentrytitle><manvolnum>1</manvolnum></citerefentry>, file. Assuming the port is called <literal>oneko</literal> and is in the <literal>games</literal> category.
Creating a <filename>.diff</filename> for a New Port
Add all the files with <command>svn add</command>. <command>cd</command> to the base of the ports tree so full paths to the changed files are included in the diff, then generate the diff with <command>svn diff</command>. For example:
<prompt>%</prompt> <userinput>svn add .</userinput>
<prompt>%</prompt> <userinput>cd ../..</userinput>
<prompt>%</prompt> <userinput>svn diff <replaceable>games/oneko</replaceable> &gt; <replaceable>oneko.diff</replaceable></userinput>
To make it easier for committers to apply the patch on their working copy of the ports tree, please generate the <filename>.diff</filename> from the base of your ports tree.
Submit <filename>oneko.diff</filename> with the <link xlink:href="https://bugs.freebsd.org/submit/">bug submission form</link>. Use product <quote>Ports &amp; Packages</quote>, component <quote>Individual Port(s)</quote>, and follow the guidelines shown there. Add a short description of the program to the Description field of the PR (perhaps a short version of <varname>COMMENT</varname>), and remember to add <filename>oneko.diff</filename> as an attachment.
Giving a good description in the summary of the problem report makes the work of port committers a lot easier. We prefer something like <quote>New port: <replaceable>category</replaceable>/<replaceable>portname</replaceable> <replaceable>short description of the port</replaceable></quote> for new ports. Using this scheme makes it easier and faster to begin the work of committing the new port.
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. A simple search form of the Problem Report database can be searched at <link xlink:href="https://bugs.freebsd.org/bugzilla/query.cgi"/>.
To get a listing of <emphasis>open</emphasis> port <acronym>PR</acronym>s, select <emphasis>Open</emphasis> and <emphasis>Ports &amp; Packages</emphasis> in the search form, then click <guibutton>[ Search ]</guibutton>.
After looking at the new port, we will reply if necessary, and commit it to the tree. The submitter's name will also be added to the list of <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/contributors/contrib-additional.html">Additional FreeBSD Contributors</link> and other files.
It is also possible to submit ports using a <citerefentry><refentrytitle>shar</refentrytitle><manvolnum>1</manvolnum></citerefentry> file. Using the previous example with the <literal>oneko</literal> port above.

Loading…

None

New source string

FreeBSD Doc / books_porters-handbookEnglish

New source string 2 weeks ago
Browse all component changes

Things to check

Unpluralised

The string is used as plural, but not using plural forms

Reset

Glossary

English English
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: sect1/para
Labels
No labels currently set.
Flags
read-only
Source string location
book.translate.xml:584
Source string age
2 weeks ago
Translation file
, string 95