Source string Read only

(itstool) path: sect1/para
Context English State
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="">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=""/>.
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.
Creating a <filename>.shar</filename> for a New Port
go to the directory above where the port directory is located, and use <command>tar</command> to create the shar archive:
<prompt>%</prompt> <userinput>cd ..</userinput>
<prompt>%</prompt> <userinput>tar cf <replaceable>oneko</replaceable>.shar --format shar <replaceable>oneko</replaceable></userinput>
<filename>oneko.shar</filename> can then be submitted in the same way as <filename>oneko.diff</filename> above.
Slow Porting
Okay, so it was not that simple, and the port required some modifications to get it to work. In this section, we will explain, step by step, how to modify it to get it to work with the ports paradigm.
How Things Work
First, this is the sequence of events which occurs when the user first types <command>make</command> in the port's directory. Having <filename></filename> in another window while reading this really helps to understand it.
But do not worry, not many people understand exactly how <filename></filename> is working... <emphasis>:-)</emphasis>
The <_:buildtarget-1/> target is run. The <_:buildtarget-2/> target is responsible for making sure that the tarball exists locally in <varname>DISTDIR</varname>. If <_:buildtarget-3/> cannot find the required files in <varname>DISTDIR</varname> it will look up the URL <varname>MASTER_SITES</varname>, which is set in the Makefile, as well as our FTP mirrors where we put distfiles as backup. It will then attempt to fetch the named distribution file with <varname>FETCH</varname>, assuming that the requesting site has direct access to the Internet. If that succeeds, it will save the file in <varname>DISTDIR</varname> for future use and proceed.
The <_:buildtarget-1/> target is run. It looks for the port's distribution file (typically a compressed tarball) in <varname>DISTDIR</varname> and unpacks it into a temporary subdirectory specified by <varname>WRKDIR</varname> (defaults to <filename>work</filename>).
The <_:buildtarget-1/> target is run. First, any patches defined in <varname>PATCHFILES</varname> are applied. Second, if any patch files named <filename>patch-<replaceable>*</replaceable></filename> are found in <varname>PATCHDIR</varname> (defaults to the <filename>files</filename> subdirectory), they are applied at this time in alphabetical order.
The <_:buildtarget-1/> target is run. This can do any one of many different things.
If it exists, <filename>scripts/configure</filename> is run.
If <varname>HAS_CONFIGURE</varname> or <varname>GNU_CONFIGURE</varname> is set, <filename>WRKSRC/configure</filename> is run.
The <_:buildtarget-1/> target is run. This is responsible for descending into the port's private working directory (<varname>WRKSRC</varname>) and building it.
The <_:buildtarget-1/> target is run. This puts the final set of built files into a temporary directory (<varname>STAGEDIR</varname>, see <xref linkend="staging"/>). The hierarchy of this directory mirrors that of the system on which the package will be installed.
The <_:buildtarget-1/> target is run. This creates a package using the files from the temporary directory created during the <_:buildtarget-2/> target and the port's <filename>pkg-plist</filename>.


No matching activity found.

Browse all component changes

Things to check


The string uses three dots (...) instead of an ellipsis character (…)



English English
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: sect1/para
Source string location
String age
a year ago
Source string age
a year ago
Translation file
books/porters-handbook.pot, string 109