* Add link for 3.x packages and fix the link for 4.0-current packages.

* Add new entry "Why can't I build this port on my 3.x-stable machine?".
* Minor style fixes (add missing </sect>'s and trim trailing whitespace.

PR:	12599
Reported by:	John Baldwin <jobaldwi@vt.edu>
This commit is contained in:
Sheldon Hearn 1999-07-12 15:00:17 +00:00
parent 861330855b
commit 68df525104
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=5208

View file

@ -1,4 +1,4 @@
<!-- $Id: applications.sgml,v 1.10 1999-05-21 02:52:40 jkoshy Exp $ --> <!-- $Id: applications.sgml,v 1.11 1999-07-12 15:00:17 sheldonh Exp $ -->
<!-- The FreeBSD Documentation Project --> <!-- The FreeBSD Documentation Project -->
<sect> <sect>
@ -41,9 +41,13 @@
<url url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/ports/i386/packages-2.2.8/" <url url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/ports/i386/packages-2.2.8/"
name="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/ports/i386/packages-2.2.8/"> name="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/ports/i386/packages-2.2.8/">
<tag>for 3.2-release/3.2-stable</tag>
<url url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/ports/i386/packages-3-stable/"
name="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/ports/i386/packages-3-stable/">
<tag>for 4.0-current</tag> <tag>for 4.0-current</tag>
<url url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/ports/i386/packages-3.0/" <url url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/ports/i386/packages-4-current/"
name="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/ports/i386/packages-3.0/"> name="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/ports/i386/packages-4-current/">
</descrip> </descrip>
<p>or your nearest local mirror site. <p>or your nearest local mirror site.
@ -54,6 +58,7 @@
at the <url url="ftp://ftp.freebsd.org/pub/FreeBSD/" at the <url url="ftp://ftp.freebsd.org/pub/FreeBSD/"
name="ftp.freebsd.org"> master site. name="ftp.freebsd.org"> master site.
</sect1>
<sect1> <sect1>
<heading>Where do I find libc.so.3.0?</heading> <heading>Where do I find libc.so.3.0?</heading>
@ -61,6 +66,7 @@
system. Please take a look at the previous section and get system. Please take a look at the previous section and get
the correct port/package for your system. the correct port/package for your system.
</sect1>
<sect1> <sect1>
<heading> <heading>
ghostscript gives lots of errors with my 386/486SX.<label id="emul"> ghostscript gives lots of errors with my 386/486SX.<label id="emul">
@ -78,6 +84,7 @@
<p><bf/NOTE/ You will need to remove the <tt/MATH&lowbar;EMULATE/ <p><bf/NOTE/ You will need to remove the <tt/MATH&lowbar;EMULATE/
option when you do this. option when you do this.
</sect1>
<sect1> <sect1>
<heading> <heading>
When I run a SCO/iBCS2 application, it bombs on <tt/socksys/. When I run a SCO/iBCS2 application, it bombs on <tt/socksys/.
@ -114,6 +121,7 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx
want the <tt/spx/ driver for a local socket X connection, define want the <tt/spx/ driver for a local socket X connection, define
<tt/SPX&lowbar;HACK/ when you compile the system. <tt/SPX&lowbar;HACK/ when you compile the system.
</sect1>
<sect1> <sect1>
<heading> <heading>
How do I configure INN (Internet News) for my machine? How do I configure INN (Internet News) for my machine?
@ -126,11 +134,10 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx
</sect1> </sect1>
<sect1> <sect1>
<heading>What version of Microsoft FrontPage should I get? <heading>What version of Microsoft FrontPage should I get?</heading>
</heading>
<p>Use the Port, Luke! A pre-patched version of Apache is available in the ports tree. <p>Use the Port, Luke! A pre-patched version of Apache is available
</p> in the ports tree.
</sect1> </sect1>
<sect1> <sect1>
@ -141,6 +148,20 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx
name="http://www.freebsd.org/java">. name="http://www.freebsd.org/java">.
</sect1> </sect1>
<sect1>
<heading>Why can't I build this port on my 3.x-stable machine?</heading>
<p>If you're running a FreeBSD version that lags significantly behind
-current or -stable, you may need a ports upgrade kit from
<url url="http://www.freebsd.org/ports"
name="http://www.freebsd.org/ports">. If you are up to date, then
someone might have committed a change to the port which works for
-current but which broke the port for -stable. Please submit a bug
report on this with the <em>send-pr(1)</em> command, since the ports
collection is supposed to work for both the -current and -stable
branches.
</sect1>
</sect> </sect>