> > 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? 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... 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 (-; ------------------------------------------------------------------------- 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
