| 7 | | Note first of all that this finds dependents of icu (i.e. those that have a dependency on icu), not dependencies of icu. Second, note that more precisely, this finds ports that have dependencies whose names contain the string "icu"; this is more than just those that depend on the port icu. For example, it would find py-pyicu and gramps (which depend on py27-pyicu, not icu) and the webkit-gtk ports (which depend on harfbuzz-icu, not icu). Finally, note that this only finds dependencies declared by default; it does not find dependencies in non-default variants or that vary by platform or other conditionals; for example, if you run the command on Mavericks or later, you'll miss sword, which depends on icu, but clears its dependencies on Mavericks and later so that it can more quickly inform the user of the fact that it is not Mavericks-compatible. I usually just grep the portfiles, which doesn't have these shortcomings. |
| | 7 | Note first of all that this finds dependents of icu (i.e. those that have a dependency on icu), not dependencies of icu. Second, note that more precisely, this finds ports that have dependencies whose names match the regular expression "icu"; this is more than just those that depend on the port icu. For example, it would find py-pyicu and gramps (which depend on py27-pyicu, not icu) and the webkit-gtk ports (which depend on harfbuzz-icu, not icu). Finally, note that this only finds dependencies declared by default; it does not find dependencies in non-default variants or that vary by platform or other conditionals; for example, if you run the command on Mavericks or later, you'll miss sword, which depends on icu, but clears its dependencies on Mavericks and later so that it can more quickly inform the user of the fact that it is not Mavericks-compatible. I usually just grep the portfiles, which doesn't have these shortcomings. |
