Tell users to get the upgrade kit if using ports-current on a release system.
Mention the list of categories in the handbook.
This commit is contained in:
parent
d44ea9af8a
commit
18bc479983
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=3754
1 changed files with 11 additions and 4 deletions
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: ports.sgml,v 1.31 1998-10-04 01:14:38 jkh Exp $ -->
|
||||
<!-- $Id: ports.sgml,v 1.32 1998-11-07 06:37:02 asami Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<chapt><heading>Installing Applications: The Ports collection<label id="ports"></heading>
|
||||
|
@ -207,7 +207,13 @@ latest version of the port you want, you will need to download the
|
|||
might sound like rather a fiddly job
|
||||
full of pitfalls, but it is actually very easy.
|
||||
<p>
|
||||
The key to it is that the FreeBSD FTP server can create on-the-fly
|
||||
First, if you are running a release version of FreeBSD, make sure you
|
||||
get the appropriate ``upgrade kit'' for your release from the <htmlurl
|
||||
url="http://www.freebsd.org/ports/" name="ports page">. These
|
||||
packages include files that have been updated since the release that
|
||||
you may need to compile new ports.
|
||||
<p>
|
||||
The key to the skeletons is that the FreeBSD FTP server can create on-the-fly
|
||||
<ref id="ports:tarball" name="tarballs"> for you. Here is how it works,
|
||||
with the gnats program in the databases directory as an example (the
|
||||
bits in square brackets are comments. Do not type them in if you are
|
||||
|
@ -284,7 +290,7 @@ installed. Here is the Makefile for ElectricFence:-
|
|||
# Date created: 13 November 1997
|
||||
# Whom: jraynard
|
||||
#
|
||||
# $Id: ports.sgml,v 1.31 1998-10-04 01:14:38 jkh Exp $
|
||||
# $Id: ports.sgml,v 1.32 1998-11-07 06:37:02 asami Exp $
|
||||
#
|
||||
|
||||
DISTNAME= ElectricFence-2.0.5
|
||||
|
@ -310,7 +316,8 @@ of human readers (as in most Unix script files).
|
|||
name="tarball">, but without the extension.
|
||||
<p>
|
||||
`CATEGORIES" states what kind of program this is. In this case, a
|
||||
utility for developers.
|
||||
utility for developers. See the <ref id="porting:categories"
|
||||
name="categories"> section of this handbook for a complete list.
|
||||
<p>
|
||||
`MASTER_SITES" is the URL(s) of the master FTP site, which is
|
||||
used to retrieve the <ref id="ports:tarball" name="tarball"> if it is not
|
||||
|
|
Loading…
Reference in a new issue