os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Replace some <link> and <xref>s which pointed to locations in to the

Browse source 
Handbook with <ulink>, which uses URLs to the same.  The porter's handbook
now builds.
This commit is contained in:
Nik Clayton 2000-05-17 18:24:15 +00:00
parent 7e5cc95a26
commit 7cafc16bb3
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=7207
2 changed files with 22 additions and 22 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
en_US.ISO8859-1/books/porters-handbook/book.sgml
View file

@ -1,7 +1,7 @@
<!-- <!--
The FreeBSD Documentation Project The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/porter-handbook/book.sgml,v 1.1 2000/04/22 23:35:54 nik Exp $ $FreeBSD: doc/en_US.ISO_8859-1/books/porters-handbook/book.sgml,v 1.97 2000/05/09 00:26:12 nik Exp $
--> -->
<!DOCTYPE BOOK PUBLIC "-//FreeBSD//DTD DocBook V3.1-Based Extension//EN" [ <!DOCTYPE BOOK PUBLIC "-//FreeBSD//DTD DocBook V3.1-Based Extension//EN" [
@ -328,8 +328,8 @@ lib/X11/oneko/mouse.xpm
directory or the <filename>pkgname.tgz</filename> package, so delete directory or the <filename>pkgname.tgz</filename> package, so delete
them now. Next, simply include the output of <command>shar `find them now. Next, simply include the output of <command>shar `find
port_dir`</command> in a bug report and send it with the port_dir`</command> in a bug report and send it with the
&man.send-pr.1; program (see <link linkend="contrib-general">Bug &man.send-pr.1; program (see <ulink url="../handbook/contrib-how.html#CONTRIB-GENERAL">Bug
Reports and General Commentary</link> for more information about Reports and General Commentary</ulink> for more information about
&man.send-pr.1;. If the uncompressed port is larger than 20KB, &man.send-pr.1;. If the uncompressed port is larger than 20KB,
you should compress it into a tarfile and use &man.uuencode.1; you should compress it into a tarfile and use &man.uuencode.1;
before including it in the bug report (uuencoded tarfiles are before including it in the bug report (uuencoded tarfiles are
@ -821,8 +821,8 @@ MASTER_SITE_SUBDIR= applications</programlisting>
--><emphasis>:-)</emphasis></para> --><emphasis>:-)</emphasis></para>
<para>For detailed description of the responsibility of maintainers, <para>For detailed description of the responsibility of maintainers,
refer to <link linkend="policies-maintainer">MAINTAINER on refer to <ulink url="../handbook/policies.html#POLICIES-MAINTAINER">MAINTAINER on
Makefiles</link> section.</para> Makefiles</ulink> section.</para>
</sect1> </sect1>
<sect1> <sect1>
@ -1346,8 +1346,8 @@ MASTERDIR= ${.CURDIR}/../xdvi300
<chapter> <chapter>
<title>Shared library versions</title> <title>Shared library versions</title>
<para>Please read our <link linkend="policies-shlib">policy on <para>Please read our <ulink url="../handbook/policies-shlib.html">policy on
shared library versioning</link> to understand what to do with shared library versioning</ulink> to understand what to do with
shared library versions in general. Do not blindly assume software shared library versions in general. Do not blindly assume software
authors know what they are doing; many of them do not. It is very authors know what they are doing; many of them do not. It is very
important that these details are carefully considered, as we have important that these details are carefully considered, as we have
@ -2043,7 +2043,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
port. You can find them in the port. You can find them in the
<filename>ports/ports-current</filename> directory of the ftp mirror <filename>ports/ports-current</filename> directory of the ftp mirror
sites. You may also use CVSup to keep your whole ports collection sites. You may also use CVSup to keep your whole ports collection
up-to-date, as described in <xref linkend="cvsup-config">.</para> up-to-date, as described in <ulink url="../handbook/synching.html#CVSUP-CONFIG">the Handbook</ulink>.</para>
<para>The next step is to send a mail to the maintainer, if one is <para>The next step is to send a mail to the maintainer, if one is
listed in the port's <filename>Makefile</filename>. That person may listed in the port's <filename>Makefile</filename>. That person may
@ -2079,8 +2079,8 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
the porting process.You should check your own port against this list, the porting process.You should check your own port against this list,
but you can also check ports in the PR database that others have but you can also check ports in the PR database that others have
submitted. Submit any comments on ports you check as described in submitted. Submit any comments on ports you check as described in
<link linkend="contrib-general">Bug Reports and General <ulink url="../handbook/contrib-how.html#CONTRIB-GENERAL">Bug Reports and General
Commentary</link>. Checking ports in the PR database will both make Commentary</ulink>. Checking ports in the PR database will both make
it faster for us to commit them, and prove that you know what you are it faster for us to commit them, and prove that you know what you are
doing.</para> doing.</para>
@ -2142,7 +2142,7 @@ post-install:
<para>Do not write anything to files outside <para>Do not write anything to files outside
<makevar>WRKDIR</makevar>. <makevar>WRKDIR</makevar> is the only <makevar>WRKDIR</makevar>. <makevar>WRKDIR</makevar> is the only
place that is guaranteed to be writable during the port build (see place that is guaranteed to be writable during the port build (see
<link linkend="ports-cd">compiling ports from CDROM</link> for an <ulink url="../handbook/ports-using.html#PORTS-CD">compiling ports from CDROM</ulink> for an
example of building ports from a read-only tree). If you need to example of building ports from a read-only tree). If you need to
modify some file in <makevar>PKGDIR</makevar>, do so by <link modify some file in <makevar>PKGDIR</makevar>, do so by <link
linkend="porting-pkgsubdir">redefining a variable</link>, not by linkend="porting-pkgsubdir">redefining a variable</link>, not by

22
en_US.ISO_8859-1/books/porters-handbook/book.sgml
View file

@ -1,7 +1,7 @@
<!-- <!--
The FreeBSD Documentation Project The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/porter-handbook/book.sgml,v 1.1 2000/04/22 23:35:54 nik Exp $ $FreeBSD: doc/en_US.ISO_8859-1/books/porters-handbook/book.sgml,v 1.97 2000/05/09 00:26:12 nik Exp $
--> -->
<!DOCTYPE BOOK PUBLIC "-//FreeBSD//DTD DocBook V3.1-Based Extension//EN" [ <!DOCTYPE BOOK PUBLIC "-//FreeBSD//DTD DocBook V3.1-Based Extension//EN" [
@ -328,8 +328,8 @@ lib/X11/oneko/mouse.xpm
directory or the <filename>pkgname.tgz</filename> package, so delete directory or the <filename>pkgname.tgz</filename> package, so delete
them now. Next, simply include the output of <command>shar `find them now. Next, simply include the output of <command>shar `find
port_dir`</command> in a bug report and send it with the port_dir`</command> in a bug report and send it with the
&man.send-pr.1; program (see <link linkend="contrib-general">Bug &man.send-pr.1; program (see <ulink url="../handbook/contrib-how.html#CONTRIB-GENERAL">Bug
Reports and General Commentary</link> for more information about Reports and General Commentary</ulink> for more information about
&man.send-pr.1;. If the uncompressed port is larger than 20KB, &man.send-pr.1;. If the uncompressed port is larger than 20KB,
you should compress it into a tarfile and use &man.uuencode.1; you should compress it into a tarfile and use &man.uuencode.1;
before including it in the bug report (uuencoded tarfiles are before including it in the bug report (uuencoded tarfiles are
@ -821,8 +821,8 @@ MASTER_SITE_SUBDIR= applications</programlisting>
--><emphasis>:-)</emphasis></para> --><emphasis>:-)</emphasis></para>
<para>For detailed description of the responsibility of maintainers, <para>For detailed description of the responsibility of maintainers,
refer to <link linkend="policies-maintainer">MAINTAINER on refer to <ulink url="../handbook/policies.html#POLICIES-MAINTAINER">MAINTAINER on
Makefiles</link> section.</para> Makefiles</ulink> section.</para>
</sect1> </sect1>
<sect1> <sect1>
@ -1346,8 +1346,8 @@ MASTERDIR= ${.CURDIR}/../xdvi300
<chapter> <chapter>
<title>Shared library versions</title> <title>Shared library versions</title>
<para>Please read our <link linkend="policies-shlib">policy on <para>Please read our <ulink url="../handbook/policies-shlib.html">policy on
shared library versioning</link> to understand what to do with shared library versioning</ulink> to understand what to do with
shared library versions in general. Do not blindly assume software shared library versions in general. Do not blindly assume software
authors know what they are doing; many of them do not. It is very authors know what they are doing; many of them do not. It is very
important that these details are carefully considered, as we have important that these details are carefully considered, as we have
@ -2043,7 +2043,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
port. You can find them in the port. You can find them in the
<filename>ports/ports-current</filename> directory of the ftp mirror <filename>ports/ports-current</filename> directory of the ftp mirror
sites. You may also use CVSup to keep your whole ports collection sites. You may also use CVSup to keep your whole ports collection
up-to-date, as described in <xref linkend="cvsup-config">.</para> up-to-date, as described in <ulink url="../handbook/synching.html#CVSUP-CONFIG">the Handbook</ulink>.</para>
<para>The next step is to send a mail to the maintainer, if one is <para>The next step is to send a mail to the maintainer, if one is
listed in the port's <filename>Makefile</filename>. That person may listed in the port's <filename>Makefile</filename>. That person may
@ -2079,8 +2079,8 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
the porting process.You should check your own port against this list, the porting process.You should check your own port against this list,
but you can also check ports in the PR database that others have but you can also check ports in the PR database that others have
submitted. Submit any comments on ports you check as described in submitted. Submit any comments on ports you check as described in
<link linkend="contrib-general">Bug Reports and General <ulink url="../handbook/contrib-how.html#CONTRIB-GENERAL">Bug Reports and General
Commentary</link>. Checking ports in the PR database will both make Commentary</ulink>. Checking ports in the PR database will both make
it faster for us to commit them, and prove that you know what you are it faster for us to commit them, and prove that you know what you are
doing.</para> doing.</para>
@ -2142,7 +2142,7 @@ post-install:
<para>Do not write anything to files outside <para>Do not write anything to files outside
<makevar>WRKDIR</makevar>. <makevar>WRKDIR</makevar> is the only <makevar>WRKDIR</makevar>. <makevar>WRKDIR</makevar> is the only
place that is guaranteed to be writable during the port build (see place that is guaranteed to be writable during the port build (see
<link linkend="ports-cd">compiling ports from CDROM</link> for an <ulink url="../handbook/ports-using.html#PORTS-CD">compiling ports from CDROM</ulink> for an
example of building ports from a read-only tree). If you need to example of building ports from a read-only tree). If you need to
modify some file in <makevar>PKGDIR</makevar>, do so by <link modify some file in <makevar>PKGDIR</makevar>, do so by <link
linkend="porting-pkgsubdir">redefining a variable</link>, not by linkend="porting-pkgsubdir">redefining a variable</link>, not by