论坛徽章:: 0

电梯直达

1楼 [收藏(0)] [报告]

发表于 2005-12-27 14:37 |只看该作者 |倒序浏览

Chapter 4 Installing Applications: Packages and Ports (2)

5.  Using the Ports Collection

5.1  Obtaining the Ports Collection
Before you can install ports, you must first obtain the Ports Collection—which is essentially a set of Makefiles, patches, and description files placed in /usr/ports.

Two ways to obtain the ports collection: Sysinstall Method and CVSup Method.

Sysinstall Method
#  sysinstall

CVSup Method
1. Install the net/cvsup port.
2. As root, copy /usr/share/examples/cvsup/ports-supfile to a new location, such /root or our home directory.
3. Edit ports-supfile.
4. Change CHANGE_THIS.FreeBSD.org to a CVSup server near you.
5. Run cvsup:
      #  cvsup –g –L 2 /root/ports-supfile
6. Running this command later will download and apply all the recent changes to your Ports Collection, except actually rebuilding the ports for your own system.

5.2  Installing  Ports
After attaining Ports Collection, you are able to install ports now. The ports includes instructions on how to build source code, but does not include the actual source code.
A port skeleton involves in Ports Collection. A port skeleton is a minimal set of files that tells your FreeBSD system how to cleanly compile and install a program. Each port skeleton includes:
1. A Makefile. Specifies how the application should be compiled and where it should be installed on your system.
2. A distinfo file. Contains information about the files that must be downloaded to build the port and their checksums, to verify that files have not been corrupted during the download using md5.
3. A files directory. This directory contains patches to make the program compile and install on your FreeBSD system. Patches are basically small files that specify changes to particular files. Patches are also known as “diffs” because they are generated by the diff program.    This directory may also contain other files used to build the port.
4. A pkg-descr file. This is a more detailed, often multiple-line, description of the program.
5. A pkg-plist file. A list of all the files that will be installed by the port. It also tells the ports system what files to remove upon deinstallation.
6. Some ports have other files, such as pkg-message. The ports system uses these files to handle special situations.

Before installing any port, you should be sure to have an up-to-date Ports Collection. A security vulnerabilities check can be automatically done by portaudit before any new application installation. Consider running portaudit –F before installing a new port, to fetch the current vulnerabilities database.

5.2.1  Installing Ports from a CD-ROM
The official CD-ROM images no longer includes distfiles. This section assumes that you have a CD disc which contains the distfiles (can be downloaded or order from other vendors).
1. Place the CD-ROM in the drive and mount it on /cdrom.
2. Change to the directory for the port you want to install:
# cd /usr/ports/sysutils/lsof
3. You would see the port skeleton. The next step is to compile, or ‘build’, the port. This is done by typing make at the prompt.
#    make
4. It would compiled the source and the next step is to install the port.
#    make install
5. Once you are returned to your prompt, you should be able to run the application you just install.
You can save an extra step by just running make install instead of make and make install as two separate steps.

After installing the port, you might have to use some commands to speed up the shell lookup operations or enable the newly installed commands can be used. These commands are:
rehash       à tcsh
hash –r à sh or shells/bash

5.2.2  Installing Ports from the Internet
You must have a working Internet connection when you install Ports from the Internet. If you do not, you will need to perform the CD-ROM installation, or put a copy of the distfiles into /usr/ports/distfiles manually.

The difference between installing from the Internet and a CD-ROM is that the distfiles is downloaded from the Internet instead of read from the CD-ROM.

The steps to install Ports from the Internet:
1. Change to the port directory you want to install:
      # cd /usr/ports/sysutils/lsof
2. Install the Port:
         # make install
Notice:
1. If you are behind a firewall, or need to use FTP/HTTP proxy, you may need to use FTP_PASSIVE-MODE, FTP_PROXY, and FTP-PASSWORD. See fetch(3) for the complete list.
2. If users cannot be connected all the time, the make fetch option is provided. Just run this command at the top level directory (/usr/ports) and lower level categories (/usr/ports/net) and the required files will downloaded. Replace fetch with fect-recursive if you want to fetch all the dependencies of a port too.
3. You can build all the ports in a category or as a whole by running make in the top level directory, just like the aforementioned make fetch method. This is dangerous, however, as some ports cannot co-exist. In other cases, some ports can install two different files with the same filename.
4. When you need to acquire the tarballs from a site other than the MASTER_SITES (the location where files are downloaded from), You can override the MASTER_SITES option with the following command:
#  cd /usr/ports/directory
#  make MASTER_SITE_OVERRIDE= \ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch
In this example we change the MASTER_SITES option to ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/.
5. Some ports allow (or even require) you to provide build options.

5.3  Overriding the Default Ports Directories
Sometimes it is useful (or mandatory) to use a different distfiles and ports directory. The PORTSDIR and PREFIX variables can override the default directories. For example:

#  make PORTSDIR=/usr/home/example/ports install
Will compile the port in /usr/home/example/ports and install everything under /usr/local.

#  make PREFIX=/usr/home/example/local install
Will compile it in /usr/ports and install it it /usr/home/example/local.

# make PORTSDIR= . . /ports PREFIX= . . /local install
Will combine the two (it is too long to completely write on this page, but it should give you the general idea). Alternatively, these variables can also be set as part of your environment.

5.4  Dealing with imake
Some ports that use imake (a part of X Windows System) do not work well with PREFIX, and will insist on installing under /usr/X11R6. Similarly some Perl ports ignore PREFIX  and install in the Perl tree. Making these ports respect PREFIX is a difficult or impossible job.

5.5  Removing Installed Ports
The steps to remove installed ports:
1. Change to the port directory
2. Uninstall the port with the make deinstall
For example:
   # cd /usr/ports/sysutils/lsof
   # make deinstall
If you want to reinstall it, you can do so by running make reinstall from the /usr/ports/sysutils/lsof directory.

The make deinstall and make reinstall sequence does not work once you have run make clean. If you want to deinstall a port after cleaning, use pkg_delete as discussed in the Packages section of the Handbook.

5.5  Ports and Disk Space
To clean up the temporary work directories after building and installing software from the ports, use the make clean command. You can also remove the source distribution files from the distfiles directory, and remove the installed ports if the need for them has passed.
Some users choose to limit the available port categories by placing an entry in the refuse file. This way, when they run the CVSup application, it will not download the files in that category. More information regarding the refuse file can be found in Section A.5.3.1

5.6 Upgrading Ports
When upgrading ports, you should update your Ports Collections first, then check the /usr/ports/UPDATING file before attempting a port upgrade. This file describes various issues and additional steps user may encounter and need to perform when updating a port.

It could be a tedious job when we upgrade a number of ports. The sysutils/portupgrate utility will do everything for us.  Just install it like you would any other port, using the make install clean command.

The steps to upgrade a number of ports:
1. Read the list of installed ports and create a database file in /var/db/pkg directory.
         #  pkgdb -F
2. Read the database and the ports INDEX file. Finally, portupgrade will begin to download, build, backup, install, and clean the ports which have been updated.
         #  portupgrade -a
3. If only a certain application to be upgraded, not the complete database, use portupgrade kpgname, include the flags –r if portupgrade should act on all those packages depending on the given package as well, and –R to act on all packages required by the given packages.
4. To use packages instead of ports for installation, provide –P. With this option portupgrade searches the local directories listed in the PKG_PATH, or fetches packages from remote site if it is not found locally. If packages cannot be found locally or fetched remotely, portupgrade will use ports. To avoid using ports, specify –PP.
5. To just fetch distfiles (or packages, if –P is specified) without building or installing anything, use –F. For more information see portupgrade.
6. It is important to regularly update the package database using pkgdb –F to fix inconsistencies, especially when portupgrade asks you to. Do not abort portupgrade while it is updating the package database, this will leave you an inconsistent database.