On Thu, May 29, 2008 at 7:00 PM, Rainer Müller <[EMAIL PROTECTED]> wrote:
> Tabitha McNerney wrote: > >> I have what might seem to be a dumb question. I noticed today that the >> MacPort named "libiconv" version 1.12 has a build dependency on another port >> named gperf, specifically: >> >> $ port deps libiconv >> >> libiconv has build dependencies on: >> >> gperf >> > Just as another side note, I made some changes to 'port deps' in trunk. If > you use the -v flag it will print the real dependency as specified in the > Portfile. > > --snip-- > > $ port -v deps libiconv > libiconv has build dependencies on: > bin:gperf:gperf > > --snap-- > > Of course, only helpful for people running trunk at the moment. Ranier this is quite helpful because I'm putting together a document for my organization which keeps track of all the ports we use and their direct dependencies (including their dependency types: build, library, run). Thanks! T.M. > > > Rainer >
_______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
