Hi there (maintainer CCed)

Am 18.07.2008 um 02:24 schrieb Chunky Kibbles:

> On Fri, Jul 18, 2008 at 12:59:06AM +0200, Martin Costabel wrote:
>> Chunky Kibbles wrote:
>>> Hola,
>>>
>>> I've just reinstalled fink from scratch. The first package I  
>>> attempted
>>> to install was libcaca [actually, second, after aalib which had  
>>> almost
>>> no dependencies]:
>>>
>>> lefty:etc chunky$ fink install libcaca-dev
>>> Information about 6992 packages read in 0 seconds.
>>>
>>> The following package will be installed or updated:
>>> libcaca-dev
>>> The following 303 additional packages will be installed:
>>
>> Try to install doxygen from binary, like
>>
>> sudo apt-get install doxygen=1.3.4-1005
>>
>> This should reduce the dependency list somewhat. If it does, please  
>> tell
>> us about it.
>
> 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?

Cheers,
Max



-------------------------------------------------------------------------
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

Reply via email to