Quoting Henrik Brix Andersen <[EMAIL PROTECTED]> (from Thu, 2 Aug
2007 16:17:10 +0200):
Feature:
- allow to only register explicit dependencies, disabled by default
(EXPLICIT_PACKAGE_DEPENDS=whatever_you_want)
Can you elaborate a bit on this new EXPLICIT_PACKAGE_DEPENDS feature?
Perhaps give a usage example or two? :)
What about diffing the output of "make actual-package-depends" and
"make actual-package-depends -DEXPLICIT_PACKAGE_DEPENDS"?
Simple Example:
Port A depends upon B
Port B depends upon C
Without the feature:
Port A registers dependencies to ports B and C
With the feature:
Port A registers dependendcy to ports B
Now think about GNOME/KDE/... and X11: a lot of GNOME/... programs
don't link directly to the X11 libs. So if you want to recompile all
programs which depend upon a specific X11 lib after an API change, you
can not find all programs by grepping around in the dependency list.
With the above feature you can do that (modulo bugs in the dependency
list), without it you recompile a lot more ports than necessary. We've
seen this happen several times in the past.
Bye,
Alexander.
--
"Microwave oven? Whaddya mean, it's a microwave oven? I've been
watching Channel 4 on the thing for two weeks."
http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
