From owner-svn-doc-head@FreeBSD.ORG Tue Feb 4 14:21:24 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 95EFF778; Tue, 4 Feb 2014 14:21:24 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 801E412A8; Tue, 4 Feb 2014 14:21:24 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s14ELONR096010; Tue, 4 Feb 2014 14:21:24 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s14ELOEt096009; Tue, 4 Feb 2014 14:21:24 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201402041421.s14ELOEt096009@svn.freebsd.org> From: Dru Lavigne Date: Tue, 4 Feb 2014 14:21:24 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43751 - head/en_US.ISO8859-1/books/handbook/ports X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Feb 2014 14:21:24 -0000 Author: dru Date: Tue Feb 4 14:21:24 2014 New Revision: 43751 URL: http://svnweb.freebsd.org/changeset/doc/43751 Log: White space fix only. Translators can ignore. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/ports/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/ports/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/ports/chapter.xml Tue Feb 4 14:11:48 2014 (r43750) +++ head/en_US.ISO8859-1/books/handbook/ports/chapter.xml Tue Feb 4 14:21:24 2014 (r43751) @@ -194,10 +194,12 @@ &a.ports; and the &a.ports-bugs;. - Before installing any application, check http://vuxml.freebsd.org/ for security issues - related to the application or install ports-mgmt/portaudit. Once - installed, type portaudit -F -a to check - all installed applications for known vulnerabilities. + Before installing any application, check http://vuxml.freebsd.org/ + for security issues related to the application or install + ports-mgmt/portaudit. Once installed, type + portaudit -F -a to check all installed + applications for known vulnerabilities. The remainder of this chapter explains how to use packages @@ -215,7 +217,8 @@ The &os; web site maintains an up-to-date searchable - list of all the available applications, at http://www.FreeBSD.org/ports/. + list of all the available applications, at http://www.FreeBSD.org/ports/. The ports can be searched by application name or by software category. @@ -223,7 +226,8 @@ FreshPorts - Dan Langille maintains FreshPorts.org + Dan Langille maintains FreshPorts.org which provides a comprehensive search utility and also tracks changes to the applications in the Ports Collection. Registered users can create a customized watch list in order @@ -235,8 +239,9 @@ Freecode If you do not know the name of an application, try - using a site like Freecode.com to - find an application, then check back at the &os; site to + using a site like Freecode.com + to find an application, then check back at the &os; site to see if the application has been ported yet. @@ -258,18 +263,18 @@ lsof: /usr/ports/sysutils/lsof /usr/ports/sysutils/lsof Note that this will also return any matched files - downloaded into the /usr/ports/distfiles - directory. + downloaded into the + /usr/ports/distfiles directory. Another way to find software is by using the Ports Collection's built-in search mechanism. To use the search - feature, cd to /usr/ports then run - make search - name=program-name - where program-name is the name - of the software. For example, to search for + feature, cd to + /usr/ports then run make + search name=program-name where + program-name is the name of the + software. For example, to search for lsof: &prompt.root; cd /usr/ports @@ -561,9 +566,11 @@ docbook = faster and easier. pkgng is not a replacement for - port management tools like ports-mgmt/portmaster or ports-mgmt/portupgrade. These - tools can be used to install third-party software from both - binary packages and the Ports Collection, while + port management tools like + ports-mgmt/portmaster or + ports-mgmt/portupgrade. These tools can be + used to install third-party software from both binary packages + and the Ports Collection, while pkgng installs only binary packages. @@ -844,12 +851,16 @@ Deinstalling ca_root_nss-3.15.1_1... don &prompt.root; pkg set -o lang/php5:lang/php53 - As another example, to update lang/ruby18 to lang/ruby19, run: + As another example, to update + lang/ruby18 to + lang/ruby19, run: &prompt.root; pkg set -o lang/ruby18:lang/ruby19 As a final example, to change the origin of the - libglut shared libraries from graphics/libglut to graphics/freeglut, run: + libglut shared libraries from + graphics/libglut to + graphics/freeglut, run: &prompt.root; pkg set -o graphics/libglut:graphics/freeglut @@ -881,7 +892,8 @@ Deinstalling ca_root_nss-3.15.1_1... don Portsnap is a fast and user-friendly tool for retrieving the Ports Collection and - is the recommended choice for most users. See for a detailed + is the recommended choice for most users. See for a detailed description of Portsnap. @@ -893,7 +905,8 @@ Deinstalling ca_root_nss-3.15.1_1... don When running Portsnap for - the first time, extract the snapshot into /usr/ports: + the first time, extract the snapshot into + /usr/ports: &prompt.root; portsnap extract @@ -901,8 +914,8 @@ Deinstalling ca_root_nss-3.15.1_1... don After the first use of Portsnap has been completed as - shown above, /usr/ports can be updated as - needed by running: + shown above, /usr/ports can be updated + as needed by running: &prompt.root; portsnap fetch &prompt.root; portsnap update @@ -915,7 +928,8 @@ Deinstalling ca_root_nss-3.15.1_1... don If more control over the ports tree is needed or if local changes need to be maintained, Subversion can be used to - obtain the Ports Collection. Refer to the + obtain the Ports Collection. Refer to the Subversion Primer for a detailed description of Subversion. @@ -946,15 +960,17 @@ Deinstalling ca_root_nss-3.15.1_1... don Check out a copy of the ports tree. For better performance, replace svn0.us-east.FreeBSD.org with a - Subversion + Subversion mirror close to your geographic location: &prompt.root; svn checkout https://svn0.us-east.FreeBSD.org/ports/head /usr/ports - As needed, update /usr/ports after the initial - Subversion checkout: + As needed, update /usr/ports after + the initial Subversion + checkout: &prompt.root; svn update /usr/ports @@ -1002,8 +1018,9 @@ Deinstalling ca_root_nss-3.15.1_1... don Some ports include pkg-message or other files to handle special situations. For more details - on these files, and on ports in general, refer to the &os; Porter's - Handbook. + on these files, and on ports in general, refer to the &os; + Porter's Handbook. The port does not include the actual source code, also known as a distfile. The extract portion @@ -1028,14 +1045,15 @@ Deinstalling ca_root_nss-3.15.1_1... don Collection as described in the previous section. Since the installation of any third-party software can introduce security vulnerabilities, it is recommended to first check - http://vuxml.freebsd.org/ for known - security issues related to the port. Alternately, if - ports-mgmt/portaudit - is installed, run portaudit -F before - installing a new port. This command can be configured to - automatically perform a security audit and an update of - the vulnerability database during the daily security system - check. For more information, refer to the manual page for + http://vuxml.freebsd.org/ + for known security issues related to the port. Alternately, + if ports-mgmt/portaudit is installed, run + portaudit -F before installing a new + port. This command can be configured to automatically + perform a security audit and an update of the vulnerability + database during the daily security system check. For more + information, refer to the manual page for portaudit and &man.periodic.8;. @@ -1044,17 +1062,19 @@ Deinstalling ca_root_nss-3.15.1_1... don connection. It also requires superuser privilege. Some third-party DVD products such as the &os; Toolkit - from freebsdmall.com + from freebsdmall.com contain distfiles which can be used to install ports without - an Internet connection. Mount the DVD on /cdrom. If you use a different - mount point, set the CD_MOUNTPTS make - variable. The needed distfiles will be automatically used - if they are present on the disk. However, the licenses of - a few ports do not allow their inclusion on the DVD. This - could be because a registration form needs to be filled out - before downloading or redistribution is not allowed. In - order to install a port not included on the DVD, a connection - to the Internet will still be required. + an Internet connection. Mount the DVD on + /cdrom. If you use a different mount + point, set the CD_MOUNTPTS make variable. + The needed distfiles will be automatically used if they are + present on the disk. However, the licenses of a few ports do + not allow their inclusion on the DVD. This could be because a + registration form needs to be filled out before downloading or + redistribution is not allowed. In order to install a port not + included on the DVD, a connection to the Internet will still + be required. To compile and install the port, change to the directory of the port to be installed, then type make @@ -1146,8 +1166,9 @@ Deinstalling ca_root_nss-3.15.1_1... don compile and install the port. - When using config-recursive, - the list of ports to configure are gathered by the + When using + config-recursive, the list of + ports to configure are gathered by the all-depends-list target. It is recommended to run make config-recursive @@ -1160,11 +1181,9 @@ Deinstalling ca_root_nss-3.15.1_1... don menu in order to add, remove, or change these options after a port has been built. One method is to cd into the directory containing the - port and type make - config. Another - option is to use make - showconfig. Another - option is to execute make + port and type make config. Another + option is to use make showconfig. + Another option is to execute make rmconfig which will remove all selected options and allow you to start over. All of these options, and others, are explained in great @@ -1179,16 +1198,14 @@ Deinstalling ca_root_nss-3.15.1_1... don complete list of supported variables. For users who cannot be connected to the Internet all - the time, make - fetch can be run - within /usr/ports, - to fetch all distfiles, or within a category, such as - /usr/ports/net, or - within the specific port skeleton. Note that if a port - has any dependencies, running this command in a category - or ports skeleton will not fetch the - distfiles of ports from another category. Instead, use - make + the time, make fetch can be run + within /usr/ports, to fetch all + distfiles, or within a category, such as + /usr/ports/net, or within the specific + port skeleton. Note that if a port has any dependencies, + running this command in a category or ports skeleton will + not fetch the distfiles of ports from + another category. Instead, use make fetch-recursive to also fetch the distfiles for all the dependencies of a port. @@ -1209,14 +1226,15 @@ ftp://ftp.organization.org/pub/FreeBSD/p &prompt.root; make WRKDIRPREFIX=/usr/home/example/ports install - will compile the port in /usr/home/example/ports and - install everything under /usr/local. + will compile the port in + /usr/home/example/ports and install + everything under /usr/local. &prompt.root; make PREFIX=/usr/home/example/local install - will compile the port in /usr/ports and install it - in /usr/home/example/local. - And: + will compile the port in /usr/ports + and install it in + /usr/home/example/local. And: &prompt.root; make WRKDIRPREFIX=../ports PREFIX=../local install @@ -1238,8 +1256,8 @@ ftp://ftp.organization.org/pub/FreeBSD/p Installed ports can be uninstalled using - pkg delete. Examples - for using is command can be found in + pkg delete. Examples for using is command + can be found in Alternately, make deinstall can be run in the port's directory: @@ -1313,13 +1331,13 @@ The deinstallation will free 229 kB portmaster - The ports-mgmt/portmaster - package or port is the recommended tool for upgrading - installed ports as it is designed to use the tools installed - with &os; without depending upon other ports. It uses the - information in /var/db/pkg/ to determine - which ports to upgrade. To install this utility as a - port: + The ports-mgmt/portmaster package or + port is the recommended tool for upgrading installed ports + as it is designed to use the tools installed with &os; + without depending upon other ports. It uses the + information in /var/db/pkg/ to + determine which ports to upgrade. To install this utility + as a port: &prompt.root; cd /usr/ports/ports-mgmt/portmaster &prompt.root; make install clean @@ -1416,8 +1434,8 @@ The deinstallation will free 229 kB Another utility that can be used to upgrade ports is - Portupgrade, which is - available as the ports-mgmt/portupgrade package + Portupgrade, which is available + as the ports-mgmt/portupgrade package or port. This utility installs a suite of applications which can be used to manage ports. However, it is dependent upon Ruby. To install the port: @@ -1439,10 +1457,9 @@ The deinstallation will free 229 kB To upgrade only a specified application instead of all available ports, use portupgrade - pkgname. It is - very important to include to first - upgrade all the ports required by the given - application: + pkgname. It is very important to include + to first upgrade all the ports required + by the given application: &prompt.root; portupgrade -R firefox @@ -1479,22 +1496,21 @@ The deinstallation will free 229 kB Using the Ports Collection will use up disk space over time. After building and installing a port, running - make clean - within the ports skeleton will clean up the temporary - work directory. If - Portmaster is used to install a + make clean within the ports skeleton will + clean up the temporary work directory. + If Portmaster is used to install a port, it will automatically remove this directory unless is specified. If Portupgrade is installed, this - command will remove all work directories found within - the local copy of the Ports Collection: + command will remove all work directories + found within the local copy of the Ports Collection: &prompt.root; portsclean -C In addition, a lot of out-dated source distribution files - will collect in /usr/ports/distfiles over time. - If Portupgrade is installed, this - command will delete all the distfiles that are no longer + will collect in /usr/ports/distfiles over + time. If Portupgrade is installed, + this command will delete all the distfiles that are no longer referenced by any ports: &prompt.root; portsclean -D @@ -1513,9 +1529,10 @@ The deinstallation will free 229 kB By default, this command is interactive and will prompt the user to confirm if a distfile should be deleted. - In addition to these commands, the ports-mgmt/pkg_cutleaves package - or port automates the task of removing installed ports that - are no longer needed. + In addition to these commands, the + ports-mgmt/pkg_cutleaves package or port + automates the task of removing installed ports that are no + longer needed. @@ -1531,9 +1548,9 @@ The deinstallation will free 229 kB Most applications install at least one default - configuration file in /usr/local/etc. The - configuration files should be reviewed and possibly edited - to meet the system's needs. + configuration file in /usr/local/etc. + The configuration files should be reviewed and possibly + edited to meet the system's needs. @@ -1545,23 +1562,24 @@ The deinstallation will free 229 kB Some applications run services which must be added - to /etc/rc.conf - before starting the application. These applications usually - install a startup script in - /usr/local/etc/rc.d. See Starting + to /etc/rc.conf before starting the + application. These applications usually install a startup + script in /usr/local/etc/rc.d. See + Starting Services for more information. Users of &man.csh.1; should run - rehash to rebuild the known binary - list in the shells PATH. + rehash to rebuild the known binary list + in the shells PATH. Use - use pkg info to determine which files, man pages, - and binaries were installed with the application. + use pkg info to determine which files, + man pages, and binaries were installed with the + application. @@ -1592,12 +1610,15 @@ The deinstallation will free 229 kB Some ports are not maintained by an individual but - instead by a mailing - list. Many, but not all, of these addresses - look like freebsd-listname@FreeBSD.org. + instead by a mailing + list. Many, but not all, of these addresses look + like freebsd-listname@FreeBSD.org. Take this into account when sending an email. - In particular, ports shown as maintained by ports@FreeBSD.org are not + In particular, ports shown as maintained by ports@FreeBSD.org are not maintained by a specific individual. Instead, any fixes and support come from the general community who subscribe to that mailing list. More volunteers are always @@ -1606,15 +1627,17 @@ The deinstallation will free 229 kB If there is no response to the email, use &man.send-pr.1; to submit a bug report using the - instructions in Writing + instructions in Writing &os; Problem Reports. - Fix it! The Porter's + Fix it! The Porter's Handbook includes detailed information on the - ports infrastructure so that you can fix the - occasional broken port or even submit your own! + ports infrastructure so that you can fix the occasional + broken port or even submit your own!