<para>See if you can figure it out.  Do not worry about the

      <para>See if you can figure it out.  Do not worry about the

	contents of the <literal>&dollar;FreeBSD&dollar;</literal>

	contents of the <literal>&dollar;FreeBSD&dollar;</literal>

	is imported to our main ports tree.  You can find a more

	is imported to our main ports tree.  You can find a more

	detailed example in the <link

	detailed example in the <link

	  linkend="porting-samplem">sample Makefile</link>

	  linkend="porting-samplem">sample Makefile</link>

	<filename>patch-ab</filename> etc, always mention the path and

	<filename>patch-ab</filename> etc, always mention the path and

	file name in patch names.</para>

	file name in patch names.</para>

	when we put the files into the ports tree, and when we check

	when we put the files into the ports tree, and when we check

	them out again, they will come out different and the patch

	them out again, they will come out different and the patch

	will fail.  RCS strings are surrounded by dollar

	will fail.  RCS strings are surrounded by dollar

	take a working piece of functionality from one project to fix

	take a working piece of functionality from one project to fix

	similar areas in another, please be careful: the resulting

	similar areas in another, please be careful: the resulting

	line patch may be full of non-functional changes.  It not only

	line patch may be full of non-functional changes.  It not only

	find out what exactly caused the problem and what you changed

	find out what exactly caused the problem and what you changed

	at all.</para>

	at all.</para>

	  <para>These variables are designed to be set by the system

	  <para>These variables are designed to be set by the system

	    administrator.  There are many that are standardized in

	    administrator.  There are many that are standardized in

	    the <ulink

	    the <ulink

	    file.</para>

	    file.</para>

	  <para>When creating a port, do not make knob names specific

	  <para>When creating a port, do not make knob names specific

	    for the benefit of end-users and to help keep the number

	    for the benefit of end-users and to help keep the number

	    of knob names down.  A list of popular knob names can be

	    of knob names down.  A list of popular knob names can be

	    found in the <ulink

	    found in the <ulink

	    file.</para>

	    file.</para>

	  <para>Knob names should reflect what the knob is and does.

	  <para>Knob names should reflect what the knob is and does.

	  section are implemented in <filename>bsd.java.mk</filename>.

	  section are implemented in <filename>bsd.java.mk</filename>.

	  If you ever think that your port needs more sophisticated

	  If you ever think that your port needs more sophisticated

	  Java support, please first have a look at the <ulink

	  Java support, please first have a look at the <ulink

	  to document the latest features.  Then, if you think the

	  to document the latest features.  Then, if you think the

	  support you are lacking would be beneficial to many other

	  support you are lacking would be beneficial to many other

	  Java ports, feel free to discuss it on the &a.java;.</para>

	  Java ports, feel free to discuss it on the &a.java;.</para>

      </table>

      </table>

      <para>More details are available in <ulink

      <para>More details are available in <ulink

	  bsd.database.mk</ulink>.</para>

	  bsd.database.mk</ulink>.</para>

    </sect1>

    </sect1>

      <screen>&prompt.user; <userinput>/usr/bin/diff something.orig something > something.diff</userinput></screen>

      <screen>&prompt.user; <userinput>/usr/bin/diff something.orig something > something.diff</userinput></screen>

    </informalexample>

    </informalexample>

      contents of the port to an entire different directory and use

      contents of the port to an entire different directory and use

      the result of the recursive &man.diff.1; output of the new and

      the result of the recursive &man.diff.1; output of the new and

      old ports directories (e.g., if your modified port directory is

      old ports directories (e.g., if your modified port directory is

      <quote>Class</quote> of your PR should be

      <quote>Class</quote> of your PR should be

      <literal>change-request</literal>.  Please mention any added or

      <literal>change-request</literal>.  Please mention any added or

      deleted files in the message, as they have to be explicitly

      deleted files in the message, as they have to be explicitly

      more than about 20KB, please compress and uuencode it;

      more than about 20KB, please compress and uuencode it;

      otherwise, just include it in the PR as is.</para>

      otherwise, just include it in the PR as is.</para>

    <para>Now that you have done all that, you will want to read about

    <para>Now that you have done all that, you will want to read about

      how to keep up-to-date in <xref linkend="keeping-up">.</para>

      how to keep up-to-date in <xref linkend="keeping-up">.</para>

	directories.  Plus it is easier for you to see what you have

	directories.  Plus it is easier for you to see what you have

	changed and to update your diff if something is modified in

	changed and to update your diff if something is modified in

	the Ports Collection from when you started to work on it until

	the Ports Collection from when you started to work on it until

	something.</para>

	something.</para>

      <screen>&prompt.user; <userinput>cd ~/my_wrkdir</userinput> <co id="my-wrkdir">

      <screen>&prompt.user; <userinput>cd ~/my_wrkdir</userinput> <co id="my-wrkdir">

&prompt.user; <userinput>cd ~/my_wrkdir/pdnsd</userinput></screen>

&prompt.user; <userinput>cd ~/my_wrkdir/pdnsd</userinput></screen>

      <calloutlist>

      <calloutlist>

	      class="directory">/usr/ports/</filename>.</para>

	      class="directory">/usr/ports/</filename>.</para>

	</callout>

	</callout>

	</callout>

	</callout>

      </calloutlist>

      </calloutlist>

      <para>While in the working directory, make any changes that you

      <para>While in the working directory, make any changes that you

	would usually make to the port.  If you add or remove a file,

	would usually make to the port.  If you add or remove a file,

      <para>Make sure that you check the port using the checklist in

      <para>Make sure that you check the port using the checklist in

	<xref linkend="porting-testing"> and

	<xref linkend="porting-testing"> and

	<xref linkend="porting-portlint">.</para>

	<xref linkend="porting-portlint">.</para>

      <calloutlist>

      <calloutlist>

	  <para>This will try to merge the differences between your

	  <para>This will try to merge the differences between your

	    letter in front of each file name indicates what was done

	    letter in front of each file name indicates what was done

	    list.</para>

	    list.</para>

	</callout>

	</callout>

      </calloutlist>

      </calloutlist>

	<tgroup cols="2">

	<tgroup cols="2">

	  <tbody>

	  <tbody>

	    </row>

	    </row>

	    <row>

	    <row>

	      <entry>The file was updated without problems (you will

	      <entry>The file was updated without problems (you will

		only see this when working against a remote

		only see this when working against a remote

		repository).</entry>

		repository).</entry>

      </table>

      </table>

      <para>If you get <literal>C</literal> as a result of

      <para>If you get <literal>C</literal> as a result of

	probably will) merge things that do not make sense.</para>

	probably will) merge things that do not make sense.</para>

      <para>The last step is to make a unified &man.diff.1;

      <para>The last step is to make a unified &man.diff.1;

      <note>

      <note>

	<para>It is important to use <option>-N</option> to ensure

	<para>It is important to use <option>-N</option> to ensure

      <para>The preferred way to tell 4.3BSD/Reno (1990) and newer

      <para>The preferred way to tell 4.3BSD/Reno (1990) and newer

	versions of the BSD code apart is by using the

	versions of the BSD code apart is by using the

	<literal>BSD</literal> macro defined in <ulink

	<literal>BSD</literal> macro defined in <ulink

	Hopefully that file is already included; if not, add the

	Hopefully that file is already included; if not, add the

	code:</para>

	code:</para>

      <para>Here is a convenient list of

      <para>Here is a convenient list of

	<literal>__FreeBSD_version</literal> values as defined in

	<literal>__FreeBSD_version</literal> values as defined in

	<ulink

	<ulink

      <table frame="none">

      <table frame="none">

	<title><literal>__FreeBSD_version</literal> Values</title>

	<title><literal>__FreeBSD_version</literal> Values</title>

      <title><filename>README.html</filename></title>

      <title><filename>README.html</filename></title>

      <para>Do not include the <filename>README.html</filename> file.

      <para>Do not include the <filename>README.html</filename> file.

	using the <command>make readme</command> command.</para>

	using the <command>make readme</command> command.</para>

      <note>

      <note>

# Whom:                        Satoshi Asami <asami@FreeBSD.org>

# Whom:                        Satoshi Asami <asami@FreeBSD.org>

#

#

# $FreeBSD$

# $FreeBSD$

when it is committed to our repository.  If upgrading a port, do not alter

when it is committed to our repository.  If upgrading a port, do not alter

#

#

[section to describe the port itself and the master site - PORTNAME

[section to describe the port itself and the master site - PORTNAME

	commits.</para>

	commits.</para>

    </sect1>

    </sect1>

      <title>The Web Interface to the Source Repository</title>

      <title>The Web Interface to the Source Repository</title>

      <para>It is possible to browse the files in the source

      <para>It is possible to browse the files in the source

	repository by using a web interface.  Changes that affect the

	repository by using a web interface.  Changes that affect the

	entire port system are now documented in the <ulink

	entire port system are now documented in the <ulink

	  CHANGES</ulink> file.  Changes that affect individual ports

	  CHANGES</ulink> file.  Changes that affect individual ports

	are now documented in the <ulink

	are now documented in the <ulink

	  UPDATING</ulink> file.  However, the definitive answer to

	  UPDATING</ulink> file.  However, the definitive answer to

	any question is undoubtedly to read the source code of <ulink

	any question is undoubtedly to read the source code of <ulink

	  bsd.port.mk</ulink>, and associated files.</para>

	  bsd.port.mk</ulink>, and associated files.</para>

    </sect1>

    </sect1>