Date: Mon, 28 Jun 2004 15:24:34 +0200 From: Oliver Eikemeier <eikemeier@fillmore-labs.com> To: Conrad J.Sabatier <conrads@cox.net> Cc: freebsd-ports@freebsd.org Subject: Re: Dependencies Message-ID: <7EBAA577-C906-11D8-9FE1-00039312D914@fillmore-labs.com> In-Reply-To: <200406280017.i5S0HMnL036712@dolphin.localnet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Conrad J. Sabatier wrote: [The original thread can be found on <http://groups.google.com/groups?threadm=0qmDc.2034$lh4.1196@newsread1.news. pas.earthlink.net>] > I've run into the same sort of thing that originally sparked your > interest > in this subject, too. Wanting to upgrade any ports that depend on > "foo", > thinking it should be only a handful, only to find that there were a > whole > slew of ports indirectly dependent on "foo" as well that got included in > portupgrade's list of ports to upgrade. > > That can be most annoying indeed. I don't know if the matter has come > up > for discussion before (probably has; just about any issue you can think > of > relating to FreeBSD has been discussed before at some point). :-) > > I'll Cc: this to the ports list and see what it generates. You may want > to tune in there. To get a list of perl modules that depend on python do awk -F\| '$1 ~ /^p5/ && $9 ~ /python/ {print $1}' /usr/ports/INDEX In these cases this is always induced by the dependency of libxml2 on python. Note that all these ports (in fact much more) run-depend on pkgconfig, which is a build tool used to determine C/C++ compiler flags for linking with shared libraries. -Oliver
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7EBAA577-C906-11D8-9FE1-00039312D914>