diff --git a/share/doc/handbook/handbook.sgml b/share/doc/handbook/handbook.sgml index df4faa152e39..4a69ef003ebe 100644 --- a/share/doc/handbook/handbook.sgml +++ b/share/doc/handbook/handbook.sgml @@ -1,4 +1,4 @@ - + The FreeBSD Documentation Project - July 9, 1995 + July 12, 1995 Welcome to FreeBSD! This handbook covers the installation and day to day use of FreeBSD Release diff --git a/share/doc/handbook/ports.sgml b/share/doc/handbook/ports.sgml index 00b7ae3827c7..7db512d93081 100644 --- a/share/doc/handbook/ports.sgml +++ b/share/doc/handbook/ports.sgml @@ -1,4 +1,4 @@ - + The Ports collection @@ -32,7 +32,7 @@ those shell scripts, Makefiles and source code ``diffs'' that are necessary to configure and compile the program under FreeBSD. This keeps the entire system down to a manageable size, with the current system having over 300 ports in the master source tree and yet taking -up no more than a few tens of megabytes. +up less than ten megabytes. How does the system compile with no source code? @@ -50,15 +50,21 @@ name="Compiling ports using an Internet connection">. Compiling ports from CDROM -

The ports collection is easy to use from CDROM, and all you need do -is create a "link tree" to it using the ``lndir'' command that comes -with the XFree86 distribution. Find a location with some -free space and create a directory there, then invoking the lndir -command with the full pathname of the ``ports'' directory on the CDROM -as an argument (this might be, for example, something like: ``lndir -/cdrom/ports''). Then you can build ports directly off the CDROM by +

The ports collection is easy to use from CDROM, and all you need to +do is to create a "link tree" to it using the lndir(1) command that +comes with the XFree86 distribution. Find a location with +some free space and create a directory there, and make a symbolic link +from /usr/ports to that directory. Then invoke the lndir(1) command with +the full pathname of the ``ports'' directory on the CDROM as an +argument (this might be, for example, something like: lndir +/cdrom/ports). Then you can build ports directly off the CDROM by building them in the link tree you've created. +Note that there are some ports for which we can't provide the original +source in the CDROM due to licensing limitations. In that case, +you'll need to look at the next section (). + Compiling ports using an Internet connection

The ports collection can also use an auto-fetch system to keep @@ -69,15 +75,16 @@ your ports collection source tree up to date, updating the central mind heavy usage of your telephone. If you don't want heavy network usage when you compile your ports tree, you can pre-fetch the necessary tarballs beforehand and put them into /usr/ports/distfiles -(or wherever DISTDIR points) by hand. A good way to see what files a -port is going to need is to cd to that port's directory and do a -``make -n fetch'' to see what it does. +by hand. A good way to see what files a port is going to need is to +cd to that ports' directory and do a make fetch-list to see what +it does. The output of make fetch-list can also be used as a +shell script to fetch the ports' tarballs at a well-connected machine. You can also chose to get the source files either from the master FTP site as defined in the relevant Makefile (in the MASTER_SITES line), or some FreeBSD mirror site also carrying a set of distfiles, as does the master FTP site on ftp.FreeBSD.org (aka ftp.cdrom.com) in -the directory /pub/FreeBSD/ports/distfiles. Note that the files in +the directory /pub/FreeBSD/distfiles. Note that the files in that directory are not guarenteed to be kept up to date - this is a volunteer project! We can't make any guarantees about the mirror sites either - they are obviously under independant control and don't @@ -92,8 +99,8 @@ going to the top of the tree and typing ``make fetch''.

Oh. You can do one of four (4) things : - Fix it yourself. Technical details can be found in the GUIDELINES file, - available from URL ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/GUIDELINES + Fix it yourself. Technical details can be found in + . 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 @@ -112,7 +119,7 @@ going to the top of the tree and typing ``make fetch''. bug! Forget it. This is the easiest for most - very few of the programs in - ports can be classed as `essential'! + ports can be classified as `essential'! Grab the pre-compiled package from a ftp server. The ``master'' package collection is in: @@ -121,7 +128,8 @@ going to the top of the tree and typing ``make fetch''. 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! + source, and a lot faster! Use the pkg_add(1) or pkg_manage(1) program to + install them to your system. I've ported a program and I want to make a port out of it. What now? @@ -133,8 +141,8 @@ going to the top of the tree and typing ``make fetch''. I've got a good port, what now? -

Upload the fixed version to freefall.cdrom.com /pub/incoming or -ftp.FreeBSD.org /pub/FreeBSD/incoming and send e-mail to +

Upload the fixed version to ftp://freefall.cdrom.com/pub/incoming or +ftp://ftp.FreeBSD.org/pub/FreeBSD/incoming and send e-mail to ports@FreeBSD.org with the filename and details. Someone on the all-volunteer `ports committee' will (hopefully) look it over and commit it to the ports collection if they like the looks of it. @@ -165,7 +173,7 @@ the weirdness can be explained properly in there (most of the current weirdness is due to the lack of assumptions about anything, which is necessary due to the generic nature of these files). Also check that you have an up-to-date copy, as the file can change from minute to -minute. A reasonably up-to-date copy can be found in: +minute. The most up-to-date copy can be found in: