On Jul 20, 2008, at 11:58 PM, Chunky Kibbles wrote: >>> A little further investigation reveals that it's actually graphviz >>> that >>> has the truly fearsome dependency list, from which all others >>> derive. >>> And of course, graphviz is listed as a dependency in doxygen. >> >> And this drags in lots of stuff, aye. >> >> But I wonder: Why does Doxygen even have to depend on graphviz? As >> far >> as I know, graphviz is only used optionally. Granted, during build >> time it checks for the presence of graphviz & the location of the >> "dot" executable. But as far as I can determine, this in turn is >> "only" needed to properly and completely build the Doxygen >> documentation. >> >> So how about patching doxygen to not use "dot", even if present, and >> then remove the graphviz dependency from doxygen? > > Because doxygen with graphiviz produces really pretty and genuinely > useful graphs. What would be more interesting would be to see if it's > possible to remove the dependency from doxygen, but then look for > dot at > runtime and use it if that configuration variable is set? >
If that were the case we'd have no problem. It's perfectly legitimate, in my view, not to force a runtime dependency if it's something that can be set up at runtime via an environment variable or a conf file. > Perhaps doxygen's configure has a --force-enable-graphviz option which > enables it even if it cannot find dot. I suspect that doxygen doesn't > actually have a "real" dependency on graphviz, just a popen(3) > somewhere... > The issue is that configure autodetects dot if present. That's a typical reason for Fink packages having large dependency lists: to force identicality of builds in such cases we tend to add auto- detected stuff to the dependencies rather than disabling it. > Of course, that wouldn't take away from the fact that graphviz is > genuinely useful, and installing *it* still boosts the dependency list > into the realm of "huge". > > Gary (-; > > And don't even get me started about doxygen depending on tetex. I'm not even sure that some of our packages that builddepend on doxygen even _use_ it. configure scripts search for it, and dot, and so I suspect that people add builddepends on doxygen and graphviz based on that; but I'm not convinced that the ultimate Fink packages all actually incorporate anything that required doxygen to be there. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Fink-devel mailing list [email protected] http://news.gmane.org/gmane.os.apple.fink.devel
