On Aug 7, 2007, at 23:30, source_changes@macosforge.org wrote:
Revision: 27554 http://trac.macosforge.org/projects/macports/changeset/27554 Author: markd@macports.org Date: 2007-08-07 21:30:45 -0700 (Tue, 07 Aug 2007)
Log Message: ----------- Add a Port Dependencies section to the Port Reference section.
Modified Paths: -------------- trunk/doc/guide/new/xml/portfileref.xml
Modified: trunk/doc/guide/new/xml/portfileref.xml
[snip]
+ <title>Non-Port Dependencies</title> + + <para>Port dependencies should refer to other MacPort ports whenever + possible. However, if satisfying a dependency with a port is not + practical or desirable for a special reason, you may specify + dependencies in the Unix standard binary, library, or a specified + path.</para>
The end of this is reading a little weird. "you may specify dependencies in the Unix standard binary, library, or a specified path"?
+ + <para>In this lib style dependency, if the file + <filename>libX11.6.2.dylib</filename> is not found in the library path + the XFree86 port will be installed to satisfy it.</para> + + <programlisting>depends_lib lib:libX11.6:XFree86</ programlisting> + + <para>In this bin style dependency, if the <filename>rrdtool</filename> + binary is not found in the binary path the port rrdtool will be + installed.</para> + + <programlisting>depends_lib bin:python:python24</ programlisting>
The paragraph talks of rrdtool, but the example shows python24. The python24 binary is not a library dependency so should not be introduced with depends_lib. It is perhaps a run-time dependency or possibly a build-time dependency.
+ + <para>In this path style dependency, if the <filename>nano</ filename> + binary is not found in the path /usr/bin/nano the nano port will be + installed.</para> + + <programlisting>depends_lib path:/usr/bin/nano:nano</ programlisting>
This should also not be shown as depends_lib because it isn't a library; it's a binary.
Ryan Schmidt <ryandesign@macports.org> writes:
+ <title>Non-Port Dependencies</title> + + <para>Port dependencies should refer to other MacPort ports whenever + possible. However, if satisfying a dependency with a port is not + practical or desirable for a special reason, you may specify + dependencies in the Unix standard binary, library, or a specified + path.</para>
The end of this is reading a little weird. "you may specify dependencies in the Unix standard binary, library, or a specified path"?
Hi Ryan, Thanks for paying attention to this. I made another try at it. See if that is better. For others, the dependency section is 5.2 here: http://geeklair.net/new_macports_guide/ Does MacPorts just check the shells's path for bin: dependencies, correct? And where exactly does it search for lib: dependecies? Also, the old guide mentions the additonal keywords:
depends_fetch depends_extract Are those still used? They seem unnecessary.
The paragraph talks of rrdtool, but the example shows python24.
Fixed that.
The python24 binary is not a library dependency so should not be introduced with depends_lib. It is perhaps a run-time dependency or possibly a build-time dependency.
+ + <para>In this path style dependency, if the <filename>nano</ filename> + binary is not found in the path /usr/bin/nano the nano port will be + installed.</para> + + <programlisting>depends_lib path:/usr/bin/nano:nano</ programlisting>
This should also not be shown as depends_lib because it isn't a library; it's a binary.
Got it. I changed the python example to depends_build and nano to depends_run. Thanks a lot for paying attention to this. Mark
participants (2)
-
markd＠macports.org
-
Ryan Schmidt