PKGDEPGRAPH(1)          NetBSD General Commands Manual          PKGDEPGRAPH(1)

NNAAMMEE
     ppkkggddeeppggrraapphh - visual representation of installed packages

SSYYNNOOPPSSIISS
     ppkkggddeeppggrraapphh [--AAaaCCccDDeeFFffggLLllooRRrrssvv] [--dd _p_k_g___d_b_d_i_r] [--ii _i_m_p_a_c_t] [--KK _p_a_c_k_a_g_e_s]
                 [--MM _m_a_k_e] [--mm _t_a_r_g_e_t] [--OO _p_a_c_k_a_g_e] [--PP _p_k_g_s_r_c_d_i_r]
                 [--SS _p_a_c_k_a_g_e] [--tt _t_a_r_g_e_t] [--UU _p_a_c_k_a_g_e] [_d_a_t_a _._._.]

DDEESSCCRRIIPPTTIIOONN
     ppkkggddeeppggrraapphh emits a _d_o_t language description of the locally installed
     packages, with the inter-dependencies reduced to a minimal set of edges.
     It scans each directory under the package database directory for files
     named _+_B_U_I_L_D___I_N_F_O and _+_R_E_Q_U_I_R_E_D___B_Y in order to gather its data.

     ppkkggddeeppggrraapphh will also read any files passed to it as arguments (or stdin
     if it is not connected to a tty), in search of output that resembles that
     of either lintpkgsrc(1) --ii, lintpkgsrc(1) --gg, audit-packages(8), or the
     output from a previous incantation of this program.

     In the latter case, ppkkggddeeppggrraapphh will recolor the graph passed as input
     based, as usual, on information about currently installed pkgs.  Packages
     that are in the input graph, but not currently installed, will be colored
     black, those that are installed will be colored green, and those that
     remain out of date for some reason will remain red.

     The graph defaults to black, but if data from lintpkgsrc(1) --ii or
     _a_u_d_i_t_-_p_a_c_k_a_g_e_s is given, or if a specific package is asserted to be out
     of date (via the --OO option), then nodes (and edges leading from them)
     will be colored in the following manner:

     green   The package is completely up to date.

     orange  The package is up to date, but some of its dependencies require
             updating.

     red     The package is out of date or has had a security advisory issued
             against it, and should be replaced.

     purple  The package was not found in the local pkgsrc tree.

     blue    The package depends on something not found in the local pkgsrc
             tree.

     black   The package has been removed and not yet replaced, or the graph
             is uncolored.  The difference between an uncolored graph and a
             graph that has been recolored almost entirely black as a result
             of removing all the packages can be visually detected by the
             color of the ppkkggddeeppggrraapphh package with which the graph was recol-
             ored.

     It is important to note that all installed packages fall into one (or
     more) of the following categories:

     installed    Any installed package.

     out of date  Any package that can be upgraded.

     stale        Any package that depends on a package that is out of date.

     leaf         Any package that is not depended on by any other package.

     Selecting the type or types of packages that are listed, and how the
     information is put to use, can be controlled by the following options:

     --AA       This option modifies the output of --RR to use pkg_add(1) to rein-
              stall deleted packages, instead of building directly from the
              pkgsrc tree.

     --aa       All packages.  This option can be specified more than once to
              augment the meaning of ``all'' as it relates to the selected
              output mode.  For the default graph output, this option has no
              effect.  When used with --mm where the default output is the list
              of out of date packages, one --aa will make ppkkggddeeppggrraapphh also list
              stale packages, and a second --aa will make it list all installed
              packages.

     --CC       Asserts --cc and adds ``CLEANDEPENDS=YES'' so that all rebuilt
              dependencies are cleaned as well.

     --cc       Inserts a ``make clean'' command in the set of instructions to
              rebuild packages (see the --RR option) after they are installed.
              The --cc option used to enable graph coloring, but now graph col-
              oring is done automatically if any coloring data is given.

     --DD       Instead of the standard graph output, ppkkggddeeppggrraapphh lists the
              packages that need to be deleted, in ``least required first''
              order, so that they can be deleted without any dependency prob-
              lems.  This is a good first step to take before rebuilding all
              your packages that are out of date (see the --RR option).  This
              option is an alias for --aass.

     --dd _p_k_g___d_b_d_i_r
              The location of the package database files.  This defaults to
              the value of the _P_K_G___D_B_D_I_R environment variable, if it is set,
              or to _@_P_K_G___D_B_D_I_R_@.

     --ee       Adds an ``existence check'' to each of the lines of sh(1) style
              output so that commands can be skipped if the package is already
              installed.

     --FF       Makes ppkkggddeeppggrraapphh emit a series of sh(1) commands that will
              fetch all the required distfiles for rebuilding out of date
              packages.  This option is an alias for --mm _f_e_t_c_h.

     --ff       Force a rebuild of all dependent packages.  This option is for
              use in conjunction with the --UU option to force a rebuild of all
              the dependencies of a package to be updated.

     --gg       Add package subgraph groupings.  This places all packages with a
              common prefix (e.g., ``p5'' or ``gimp'') in a subgraph with a
              line around it so you can visually associate packages.

     --ii _i_m_p_a_c_t
              Specify the impact you want to allow when rebuilding packages.
              The impact of a given package being rebuilt is a number that
              reflects the longest path from the ``top'' of the installed
              packages (those packages upon which most other packages depend)
              to the ``bottom'' of the installed packages (those packages upon
              which no other packages depend).  A package that needs to be
              rebuilt but has nothing above it in the tree requiring rebuild-
              ing and nothing below it has an impact of 0.  Values of 10 or
              more for _i_m_p_a_c_t will probably eliminate nothing from the rebuild
              list.  The value for _i_m_p_a_c_t can also be the name of a package to
              be avoided when constructing the list of things to be rebuilt.

     --KK _p_a_c_k_a_g_e_s
              The base location or url from which to install binary packages.
              This defaults to the value of PKG_PATH, or to PACKAGES with
              ``/All'' added to the end, or to the value determined for pkgsr-
              cdir (see the --PP option) with ``/packages/All'' appended to it.

     --LL       Limit the graph to those packages that are out of date or ulti-
              mately depend on some package that is.  When used with --mm or --ss,
              this limits the list to ``leaf'' packages that are out of date
              or stale.

     --ll       Adds package ``location'' information to the labels on the
              nodes.  This is the path to the package under the local pkgsrc
              tree.

     --MM _m_a_k_e  Sets the name or path of the proper make(1) program for the
              sh(1) commands generated by the --RR and --FF options.  Some systems
              may have more than one make(1) command or the correct choice
              might not be named ``make''.  The default value for this is
              taken from the MAKE environment variable, if it is set, or is
              simply ``make''.

     --mm _t_a_r_g_e_t
              Emits generic sh(1) commands to ``make _t_a_r_g_e_t'' for each listed
              package.  One interesting target to specify is _'_$_*_' since that
              will yield a script that will pass its own command line argu-
              ments to make for processing.

     --OO _p_a_c_k_a_g_e
              Marks _p_a_c_k_a_g_e as out of date so that you can see the impact of
              deleting dependent packages and rebuilding everything.  This
              option can be used as a quick alternative to using the output
              from lintpkgsrc(1) --ii for graph coloring information.

     --oo       Adds a package ``order'' number to each node's label.  The num-
              ber indicates only the place of the node in the hierarchy, such
              that each node has a number greater than that of anything which
              depends on it, and with the ``leaf'' nodes numbered one.

     --PP _p_k_g_s_r_c_d_i_r
              The root of the pkgsrc source tree.  This defaults to the value
              of the _P_K_G_S_R_C_D_I_R environment variable, if it is set, or to
              _@_P_K_G_S_R_C_D_I_R_@.

     --RR       Instead of the standard graph output, emits a series of sh(1)
              commands that will rebuild all the out of date packages by
              rebuilding all the deleted leaf packages.  Packages that are out
              of date should be deleted first (see the --DD option).  This
              option is an alias for --eeLLmm _t_a_r_g_e_t.  See the --tt option for a
              description of what value is used for _t_a_r_g_e_t.

     --rr       Reverses the order in which the packages are listed.

     --SS _p_a_c_k_a_g_e
              Selects a subgraph of the installed package base around which to
              generate output.  By default, if a subgraph of _p_a_c_k_a_g_e is
              requested, only _p_a_c_k_a_g_e and those packages immediately above and
              below it in the graph will be listed.  To select only those
              immediately below, prefix a ``-'' to the package name.  To
              select all packages below _p_a_c_k_a_g_e, prefix ``--'' to the package
              name.  To select packages above _p_a_c_k_a_g_e, use ``+'' and ``++'' as
              appropriate.  To select all packages remotely connected to
              _p_a_c_k_a_g_e, add ``='' to the beginning.  Note: take care when using
              this option with generated lists or sh scripts.  Since the sub-
              graph of packages selected by this option may not include all
              stale or out of date packages involved in a proper package
              update procedure, the lists may be incomplete and can cause
              problems.

     --ss       Print a simple list of packages instead of sh(1) commands.  The
              default output set for this command is out of date packages from
              the entire package set.  Use combinations of --aa, --LL, --OO _p_a_c_k_a_g_e,
              and --SS _p_a_c_k_a_g_e to select more or other package lists.

     --tt _t_a_r_g_e_t
              Changes the target of the --RR output from ``install'' to _t_a_r_g_e_t
              in case you want to ``make package'' or some other target.

     --UU _p_a_c_k_a_g_e
              Generates a graph with only the out of date dependencies of
              _p_a_c_k_a_g_e marked in red (ie, packages that are out of date but not
              dependencies of _p_a_c_k_a_g_e will not be considered out of date).
              This will show the entire effect of deleting all related pack-
              ages in order to update the dependencies of the given package.
              If the --ff option is used, then all the dependencies of _p_a_c_k_a_g_e
              will be marked as out of date and the effect on the installed
              package base will be accordingly greater.

     --vv       Adds the package version number to the node's label in the
              graph.

EENNVVIIRROONNMMEENNTT
   MMAAKKEE
     The default name for the ``make'' program used in the sh(1) commands gen-
     erated by the --FF and --RR output modes.

   PPKKGG__DDBBDDIIRR
     Where to find registered packages instead of _@_P_K_G___D_B_D_I_R_@.

   PPKKGGSSRRCCDDIIRR
     Where the pkgsrc tree is located instead of _@_P_K_G_S_R_C_D_I_R_@.

   PPKKGG__PPAATTHH
   PPAACCKKAAGGEESS
     Two variables that can be used as a location for binary packages.  See
     the --AA and --KK options for more details.

EEXXAAMMPPLLEESS
     The default output:

           $ pkgdepgraph | dotty -

     To generate graph output for later use, and a postscript image of it:

           $ lintpkgsrc -i > pkgdepgraph.in
           $ audit-packages >> pkgdepgraph.in
           $ pkgdepgraph -lv pkgdepgraph.in > pkgdepgraph.dot
           $ dot -Tps pkgdepgraph.dot > pkgdepgraph.ps

     To generate a graph of just the out of date nodes as a gif:

           $ pkgdepgraph -L pkgdepgraph.in > out-of-date.dot
           $ dot -Tgif out-of-date.dot > out-of-date.gif

     To make a list of packages that need to be removed in order to bring all
     packages up to date:

           $ pkgdepgraph -D pkgdepgraph.in > delete_order
           $ pkgdepgraph -R pkgdepgraph.in > rebuild.sh

     To rebuild everything that has no other rebuild requirements:

           $ pkgdepgraph -D pkgdepgraph.in -i0 > delete_order
           $ pkgdepgraph -R pkgdepgraph.in -i0 > rebuild.sh

     Or, to rebuild everything except those things that would require rebuild-
     ing perl:

           $ pkgdepgraph -D pkgdepgraph.in -iperl > delete_order
           $ pkgdepgraph -R pkgdepgraph.in -iperl > rebuild.sh

     To subsequently delete all out of date and stale packages:

           $ pkg_delete `cat delete_order`
           $ sh rebuild.sh

     You may also find it useful to ``pre-fetch'' all the required distfiles
     for the rebuild as below, so that you can do all the rebuilding while
     off-line:

           $ pkgdepgraph -F pkgdepgraph.in > fetch.sh
           $ sh fetch.sh

     Running the rebuild script will probably take a while, but if you need to
     stop it or it stops by itself for any reason, you can rerun the script,
     and it will pick up where it left off.  If there are certain packages
     that you want installed before others are reinstalled, feel free to
     reorder the lines in the script.

     You can also ``make clean'' wherever you like when the rebuild script is
     not running, or even update your tree in between runs of the script,
     though in the latter case, it would be prudent to resume the script in
     the following manner so that any packages that are newly out of date are
     removed and replaced.

           $ pkgdepgraph -D pkgdepgraph.in > delete_order
           $ pkgdepgraph -R pkgdepgraph.in >> rebuild.sh
           $ pkg_delete `cat delete_order`
           $ sh rebuild.sh

     It is important to note that if you have specifically installed a partic-
     ular package that is a dependency, and another package (or other pack-
     ages) exist that can satisfy the same dependency, you should probably
     pre-install that particular package.  There is no guarantee that the typ-
     ical processing order will install the same package.

     A similar task is to update all the out of date dependencies of an pack-
     age, rebuild the package, and any others that might share the same depen-
     dencies:

           $ pkgdepgraph -U mozilla -D pkgdepgraph.in > delete_order
           $ pkgdepgraph -U mozilla -R pkgdepgraph.in > rebuild.sh
           $ pkg_delete `cat delete_order`
           $ sh rebuild.sh

     Or perhaps to rebuild a specific package and all packages which depend on
     it:

           $ pkgdepgraph -O glib -D > delete_order
           $ pkgdepgraph -O glib -R > rebuild.sh
           $ pkg_delete `cat delete_order`
           $ sh rebuild.sh

     Finally, to see the current state of the installed packages after some
     packages have been deleted, and some (but perhaps not all) have been
     reinstalled:

           $ pkgdepgraph out-of-date.dot | dot -Tps > current.ps

SSEEEE AALLSSOO
     dot(1), dotty(1), lintpkgsrc(1)

AAUUTTHHOORRSS
     Andrew Brown <atatat@netbsd.org>

BBUUGGSS
     ppkkggddeeppggrraapphh was written in perl(1), but I believe the balance of code
     layout and comments is actually reasonable, despite what you may think of
     perl.

     The ``rebuild'' output, ``fetch'' output, and the generic ``make target''
     output (see the --RR, --FF, and --mm options) do not deal very well with pack-
     ages that have moved within the pkgsrc tree.  Feeding the output of
     lintpkgsrc(1) --gg to ppkkggddeeppggrraapphh can offset this (it contains the current
     paths to all packages under _P_K_G_S_R_C_D_I_R) but sometimes is necessary that
     you edit the generated scripts by hand to work around this.

NetBSD 2.0                       July 28, 2004                      NetBSD 2.0