Style police.
This commit is contained in:
parent
da2f986419
commit
31bbbf3e7a
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=2315
1 changed files with 10 additions and 24 deletions
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: ports.sgml,v 1.28 1997-12-06 01:35:40 jraynard Exp $ -->
|
||||
<!-- $Id: ports.sgml,v 1.29 1997-12-29 04:29:17 jkh Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<chapt><heading>Installing Applications: The Ports collection<label id="ports"></heading>
|
||||
|
@ -336,7 +336,7 @@ installed. Here is the Makefile for ElectricFence:-
|
|||
# Date created: 13 November 1997
|
||||
# Whom: jraynard
|
||||
#
|
||||
# $Id: ports.sgml,v 1.28 1997-12-06 01:35:40 jraynard Exp $
|
||||
# $Id: ports.sgml,v 1.29 1997-12-29 04:29:17 jkh Exp $
|
||||
#
|
||||
|
||||
DISTNAME= ElectricFence-2.0.5
|
||||
|
@ -423,28 +423,16 @@ DESCR - a more detailed description.
|
|||
PLIST - a list of all the files that will be created when the program is installed.
|
||||
</itemize>
|
||||
|
||||
<sect><heading>It Does Not Work?!<label id="ports:kaput"></heading>
|
||||
<sect><heading>What to do when a port does not work.<label id="ports:troubleshooting"></heading>
|
||||
|
||||
<p>Oh. You can do one of four (4) things :
|
||||
|
||||
<enum>
|
||||
<item> Fix it yourself. Technical details can be found in
|
||||
<item> Fix it yourself. Technical details on how ports work can be found in
|
||||
<ref id="porting" name="Porting applications.">
|
||||
<item> Gripe. This is done by e-mail *ONLY*! The people at Walnut Creek are
|
||||
in no way responsible for the functionality (or lack thereof) of the
|
||||
FreeBSD system as a whole, and especially the ports system, which
|
||||
is mainly contributed by 3rd parties. (If you do not believe me, check
|
||||
the catalogue, especially the line saying "We cannot offer tech-support
|
||||
on this product")
|
||||
|
||||
The e-mail address is the &a.ports;. Please include
|
||||
details of the port, where you got both the port source &
|
||||
distfile(s) from, and what the error was.
|
||||
|
||||
Note: At time of writing, lang/Sather does not seem to work on Pentium
|
||||
machines due to the Intel Curse (aka the Floating Point Division Bug).
|
||||
Please do not tell us about this - gripe to Intel instead - it is their
|
||||
bug!
|
||||
<item> Gripe. This is done by e-mail *ONLY*! Send such e-mail to the &a.ports;
|
||||
and please include the name/version of the port, where you got both the port
|
||||
source & distfile(s) from, and what the text of the error was.
|
||||
|
||||
<item> Forget it. This is the easiest for most - very few of the programs in
|
||||
ports can be classified as `essential'!
|
||||
|
@ -452,13 +440,11 @@ PLIST - a list of all the files that will be created when the program is install
|
|||
<item> Grab the pre-compiled package from a ftp server. The ``master'' package
|
||||
collection is on FreeBSD's FTP server in the <htmlurl
|
||||
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/packages/"
|
||||
name="packages directory.">
|
||||
|
||||
though check your local mirror first, please!
|
||||
name="packages directory">, though check your local mirror first, please!
|
||||
|
||||
These are more likely to work (on the whole) than trying to compile from
|
||||
source, and a lot faster! Use the <tt>pkg_add(1)</tt>
|
||||
dddprogram to install them to your system.
|
||||
source and a lot faster besides! Use the <tt>pkg_add(1)</tt>
|
||||
program to install a package file on your system.
|
||||
|
||||
</enum>
|
||||
|
||||
|
|
Loading…
Reference in a new issue