Changeset 37495 for trunk/doc-new


Ignore:
Timestamp:
Jun 10, 2008, 2:28:00 AM (11 years ago)
Author:
markd@…
Message:

Minor text refinements.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc-new/guide/xml/portfile-dependencies.xml

    r37493 r37495  
    99  for a given port are called a port's <quote>dependencies</quote>.</para>
    1010
    11   <para>There are three ways to specify dependencies in a Portfile: library,
    12   build, and run dependencies. Specifying dependencies correctly is important
    13   for proper port upgrade and uninstall behavior. For example, you may not
    14   uninstall a port that is a library dependency for another port, though you
    15   may remove one with a build dependency; likewise, upgrading a port will
    16   upgrade its library and build dependencies also, but not its run
     11  <para>The three keywords used when specifying dependencies in a Portfile are
     12  related to port install phases, and they refer to what are called library,
     13  build, and run dependencies. Though all of them install dependencies before
     14  a given port is installed, specifying dependencies with the correct keyword
     15  is important for proper port upgrade and uninstall behavior. For example,
     16  you may not uninstall a port that is a library dependency for another port,
     17  though you may remove one with a build dependency; likewise, upgrading a
     18  port will upgrade its library and build dependencies also, but not its run
    1719  dependencies.</para>
    1820
     
    4446      <listitem>
    4547        <para>The list of dependencies to check before phases
    46         <option>configure</option>,
    47         <option>build</option>, <option>destroot</option>,
    48         <option>install</option>, and <option>package</option>. Build
    49         dependencies are needed when software is compiled, but not needed at
    50         all once the software is compiled and installed.</para>
     48        <option>configure</option>, <option>build</option>,
     49        <option>destroot</option>, <option>install</option>, and
     50        <option>package</option>. Build dependencies are needed when software
     51        is compiled, but not needed at all once the software is compiled and
     52        installed.</para>
    5153      </listitem>
    5254    </varlistentry>
     
    7173    <title>Port and File Dependencies</title>
    7274
    73     <para>Port dependencies can be satisfied by reference to a port (in this
    74     case the MacPorts' registry is queried), or by reference to a file
    75     (whether provided by a port or not). The most commonly-used type of
    76     dependencies in Portfiles are port dependencies, because dependencies
    77     should be provided by MacPorts ported software whenever possible, and
    78     usually only one port can provide the needed libraries and files.</para>
     75    <para>There are two types of dependencies: port dependencies and file
     76    dependencies. Port dependencies can be satisfied by reference to a port
     77    (the MacPorts' registry is queried), or by reference to a file (whether
     78    provided by a port or not). The most commonly-used type of dependencies in
     79    Portfiles are port dependencies, because dependencies should be provided
     80    by MacPorts ported software whenever possible, and usually only one port
     81    can provide the needed libraries and files.</para>
    7982
    8083    <para>But when satisfying a dependency with vendor-supplied software is
    81     preferred for justifiable reasons, or when it is possible for more than
    82     one port to satisfy a dependency, then file dependencies may be used. An
     84    preferred for special reasons, or when it is possible for more than one
     85    port to satisfy a dependency, then file dependencies may be used. An
    8386    example of the former is with X11 —Apple's is widely preferred; an example
    8487    of the latter is with "-devel" named ports —these ports provide identical
    85     files (only one can be activated at a time).</para>
     88    files (though only one can be activated at a time).</para>
    8689
    8790    <para>Port dependencies, the preferred type, are specified as shown in
     
    109112
    110113    <note>
    111       <para> When using lib dependencies, only the library name is specified
    112       —not its extension (e.g. ".dylib" ".so", etc.).</para>
     114      <para>When using lib dependencies, only the library name is specified
     115      —not its extension. (e.g. ".dylib" ".so", etc.)</para>
    113116    </note>
    114117  </section>
Note: See TracChangeset for help on using the changeset viewer.