Date: Fri, 11 Mar 2016 06:41:47 +0000 (UTC) From: Benedict Reuschling <bcr@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r48368 - head/en_US.ISO8859-1/books/handbook/ports Message-ID: <201603110641.u2B6fl1A093242@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: bcr Date: Fri Mar 11 06:41:46 2016 New Revision: 48368 URL: https://svnweb.freebsd.org/changeset/doc/48368 Log: Remove a commented out section anout pkg_ from the ports chapter. Reviewed by: wblock Committed at: AsiaBSDcon DevSummit 2016 Differential Revision: https://reviews.freebsd.org/D4648 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 Fri Mar 11 03:15:43 2016 (r48367) +++ head/en_US.ISO8859-1/books/handbook/ports/chapter.xml Fri Mar 11 06:41:46 2016 (r48368) @@ -391,234 +391,6 @@ Info: Lists information about open fil </itemizedlist> </sect1> - <!-- - <sect1 xml:id="packages-using"> - <sect1info> - <authorgroup> - <author> - <firstname>Chern</firstname> - <surname>Lee</surname> - <contrib>Contributed by </contrib> - </author> - </authorgroup> - </sect1info> - - <title>Using Binary Packages</title> - - <para>At the present time, &os; is transitioning toward a new - method of package management. Users - may wish to investigate the benefits of using - <link linkend="pkgng-intro">pkg</link> to manage third-party - software on &os;. This section describes the traditional method - for managing binary packages and only applies to those users - who have not yet migrated to the - <application>pkg</application> format.</para> - - <para>This method of package management uses a package database - directory, <filename>/var/db/pkg</filename>, - to track installed software versions and the files installed - with each application. Several utilities interact with the - database directory and are used to manage binary packages. - These commands begin with <literal>pkg_</literal>. This section - provides an overview of the commands which are used to install, - delete, and gather information about binary packages. Each - command provides many switches to customize its operation. - Refer to the listed man pages for more details and further usage - examples.</para> - - <sect2> - <title>Installing a Package</title> - - <indexterm> - <primary>packages</primary> - <secondary>installing</secondary> - </indexterm> - - <indexterm> - <primary><command>pkg_add</command></primary> - </indexterm> - <para>To install a binary package from a local &os; media or - a remote &os; package server, use &man.pkg.add.1;. While a - &os; media can provide a source of local packages without - requiring a network connection, it may not contain the latest - versions of binary packages as new versions are always being - rebuilt for the &os; package servers. To install from a - package server, always include <option>-r</option> (for - remote) with &man.pkg.add.1;. This automatically determines - the correct object format and release, and then fetches and - installs the package from a package server without any - further user intervention.</para> - - <indexterm> - <primary><command>pkg_add</command></primary> - </indexterm> - <screen>&prompt.root; <userinput>pkg_add -r <replaceable>lsof</replaceable></userinput></screen> - - <para>In this example, <literal>lsof</literal> is used without - specifying a version number as the version is not included - when the remote fetching feature is used. To specify an - alternative &os; FTP mirror, specify the mirror in the - <envar>PACKAGESITE</envar> environment variable. - &man.pkg.add.1; uses &man.fetch.3; to download files, which - uses various environment variables, including - <envar>FTP_PASSIVE_MODE</envar>, <envar>FTP_PROXY</envar>, - and <envar>FTP_PASSWORD</envar>. You may need to set one or - more of these if you are behind a firewall, or need to use - an FTP/HTTP proxy. See &man.fetch.3; for the complete list - of FTP-related variables.</para> - - <note> - <para>&man.pkg.add.1; will automatically download the latest - version of the application if you are using &os.current; or - &os.stable;. If you run a -RELEASE version, it instead - installs the version of the package that was built with that - release. It is possible to change this behavior by - overriding <envar>PACKAGESITE</envar>. For example, on a - &os; 9.1-RELEASE system, by default &man.pkg.add.1; - will try to fetch packages from - <literal>ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9.1-release/Latest/</literal>. - To force &man.pkg.add.1; to download &os; 9-STABLE - packages, set <envar>PACKAGESITE</envar> to - <literal>ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9-stable/Latest/</literal>.</para>; - </note> - - <para>Package files are distributed in the - <filename>.tbz</filename> format. Packages are available - from <uri - xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/">ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/</uri>; - or the <filename>/packages</filename> directory of the &os; - DVD distribution. The layout of the packages directory is - similar to that of the <filename>/usr/ports</filename> tree. - Each category has its own directory, and every package can be - found within the <filename>All</filename> directory.</para> - </sect2> - - <sect2> - <title>Managing Packages</title> - - <indexterm> - <primary>packages</primary> - <secondary>managing</secondary> - </indexterm> - - <para>To list and describe - installed packages, use &man.pkg.info.1;:</para> - - <indexterm> - <primary><command>pkg_info</command></primary> - </indexterm> - - <screen>&prompt.root; <userinput>pkg_info</userinput> -colordiff-1.0.13 Tool to colorize diff output -docbook-1.4 Meta-port for the different versions of the DocBook DTD -...</screen> - - <para>To receive a summary of the versions of all installed - packages and a comparison of the installed package versions - to the current versions found in the locally installed ports - tree, use &man.pkg.version.1;:</para> - - <indexterm> - <primary><command>pkg_version</command></primary> - </indexterm> - <screen>&prompt.root; <userinput>pkg_version</userinput> -colordiff = -docbook = -...</screen> - - <para>The symbols in the second column indicate the relative - age of the installed version and the version available in the - local ports tree.</para> - - <informaltable frame="none" pgwide="1"> - <tgroup cols="2"> - <thead> - <row> - <entry>Symbol</entry> - <entry>Meaning</entry> - </row> - </thead> - - <tbody> - <row> - <entry>=</entry> - <entry>The version of the installed package matches the - one in the local ports tree.</entry> - </row> - - <row> - <entry><</entry> - <entry>The version of the installed package is older - than the one in the local ports tree.</entry> - </row> - - <row> - <entry>></entry> - <entry>The version of the installed package is newer - than the one in the local ports tree, meaning - that the local ports tree is probably out of - date.</entry> - </row> - - <row> - <entry>?</entry> - <entry>The installed package cannot be found in the - ports index. This can happen when an installed port - is removed from the Ports Collection or is - renamed.</entry> - </row> - - <row> - <entry>*</entry> - <entry>There are multiple versions of the - package.</entry> - </row> - - <row> - <entry>!</entry> - - <entry>The installed package exists in the index but for - some reason <command>pkg_version</command> was unable - to compare the version number of the installed package - with the corresponding entry in the index.</entry> - </row> - </tbody> - </tgroup> - </informaltable> - </sect2> - - <sect2> - <title>Deleting a Package</title> - - <indexterm> - <primary><command>pkg_delete</command></primary> - </indexterm> - - <indexterm> - <primary>packages</primary> - <secondary>deleting</secondary> - </indexterm> - - <para>To remove a previously installed software package, use - &man.pkg.delete.1;:</para> - - <screen>&prompt.root; <userinput>pkg_delete <replaceable>xchat-2.8.8_1</replaceable></userinput></screen> - - <para>Note that &man.pkg.delete.1; requires the full package - name and number and that the above command would not work if - <replaceable>xchat</replaceable> was given instead of - <replaceable>xchat-2.8.8_1</replaceable>. Use - &man.pkg.version.1; to find the version of the installed - package, or use a wildcard:</para> - - <screen>&prompt.root; <userinput>pkg_delete <replaceable>xchat\*</replaceable></userinput></screen> - - <para>in this case, all packages whose names start with - <literal>xchat</literal> will be deleted.</para> - </sect2> - </sect1> - --> - <sect1 xml:id="pkgng-intro"> <title>Using <application>pkg</application> for Binary Package Management</title>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201603110641.u2B6fl1A093242>