Whatever this is, this is a very recent change that only showed up a  
few days ago when I did an update-all.
-gideon

On Jul 17, 2008, at 1:17 AM, Daniel Macks wrote:

> On Wed, Jul 16, 2008 at 09:25:34PM -0600, Jean-Fran?ois Mertens wrote:
>>
>> On 16 Jul 2008, at 15:06, Daniel Macks wrote:
>>
>>> On Wed, Jul 16, 2008 at 10:57:37PM +0200, Martin Costabel wrote:
>>>> Gideon Simpson wrote:
>>>>> So I tried blowing away my fink installation, rebuilt from  
>>>>> sources,
>>>>> updated, and with the unstable tree, some packages, such as
>>>>> imagemagick, seem to want tetex and octave.
>>>>
>>>> The culprit is probably the swig package which is a dependency of
>>>> graphviz which is a dependency of doxygen which is a dependency  
>>>> of...
>>>> basically everything. Since a while, the swig package has had a
>>>> completely insane list of dependencies including every known
>>>> programming
>>>> language.
>>>>
>>>> I don't know if swig really needs to have all this stuff  
>>>> installed on
>>>> the build host, but if it does, we need (at least) two variants of
>>>> swig,
>>>> one that can serve as dependency for graphviz and some other
>>>> packages,
>>>> and another one for the use of swig freaks that want all those
>>>> bindings.
>>>
>>> I worked on graphviz for pangocairo, and it appears that some
>>> language-bindings are optional. I don't actually *know* anything  
>>> about
>>> swig or graphviz inner workings, but:
>>>
>>> 1. swig is only a _Build_Depends of graphviz, so having a binary of
>>> graphviz would mean that swig (and its giant dep chain) is not  
>>> needed.
>>>
>>> 2. swig is only used for certain language-bindings, not the main
>>> graphviz programs. And those might even be pure plugins, so they are
>>> great candidates to move into external packages (instead of having
>>> "full" and "stubby" variants of graphviz or something like that).
>>
>> I remember from previous versions of swig that one did not have to
>> have all (or even : any...) of those languages installed to build a
>> fully-enabled swig;
>> configure was just testing them, and at worst it might affect e.g.
>> the build of
>> some example files..
>> Might be worth to investigate whether this is no longer true, before
>> changing
>> a number of other pkgs.
>
> Ooh, good thought! I'll hold off adjusting graphviz for the moment.
>
> dan
>
> -- 
> Daniel Macks
> [EMAIL PROTECTED]
> http://www.netspace.org/~dmacks
>
>
> -------------------------------------------------------------------------
> 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-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/fink-users


-------------------------------------------------------------------------
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-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to