Date: Fri, 23 Nov 2007 14:42:30 -0600 From: Stephen Montgomery-Smith <stephen@math.missouri.edu> To: Andrew Pantyukhin <infofarmer@freebsd.org> Cc: Lapo Luchini <lapo@lapo.it>, freebsd-ports@freebsd.org Subject: Re: how to distinguish direct/indirect requirements? Message-ID: <20071123204230.GA13043@cauchy.math.missouri.edu> In-Reply-To: <20071123202524.GS66812@amilo.cenkes.org> References: <fi67ng$a18$1@ger.gmane.org> <20071123202524.GS66812@amilo.cenkes.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Nov 23, 2007 at 11:25:25PM +0300, Andrew Pantyukhin wrote: > On Fri, Nov 23, 2007 at 10:49:35AM +0100, Lapo Luchini wrote: > > Is there a way to discriminate direct dependencies fro indirect > > ones, except from reading every single Makefile? (and knowing > > to full extent what USE_GNOME and similar lines really do take > > in as deps) > > You can cd some/port/&&make depends, but personally, I've also > always thought that the difference between direct and indirect > dependencies should be embedded in the package system. Haven't been following this thread, so apologies if I misunderstand or repeat. If you want only the direct depends, you can do this (under sh or bash) cd the-port for a in `make -V _LIB_RUN_DEPENDS` do (cd `echo $a | sed -E 's/.*://'` && make -V PKGNAME); done
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071123204230.GA13043>