RFE: graphviz-2.6 needs explicit dependency on guile and java

[n3npq@…]

The graphviz configure will happily build with or without scheme/java components depending on whether the appropriate ports are installed or not.

How graphviz builds should be tracked explicitly through dependencies (or variants?) for reproducuibility.

[gwright@…]

What I think I will do is disable all language bindings by default. (It's not just scheme and Java, but Python and Ocaml and who knows what else.) Graphviz tries to be too clever and builds binding for every supported language it can find.

I'll probably split up the language bindings into common (Java, guile, maybe Python) and advanced (Ocaml and whatever else). If anyone has an opinion on this they should make their comments in the next couple of days.

-Greg

[n3npq@…]

Disabling everything will "work", but leads to endless RFE's usually.

All I care is reproducible.

[gwright@…]

I'll put in a subset of the languages as dependencies but graphviz will build bindings for guile, c#, php, ruby, ocaml, java and perl. It's not reasonable to make all of them dependencies, especially since no core functionality depends on them.

This will take a while since graphviz provides no way of selectively enabling or disabling language bindings :-( This will have to be added to configure.ac. I will submit the changes upstream.

-Greg

[gwright@…]

I'm marking this bug as LATER. It's not really a DP problem, since the non-reproducibility exists on all platforms. When 2.7 is released (which should finally have a SVG rendering plugin that will work on OS X), I'll check if the configure script can support enabling/disabling specific language bindings.

-Greg

[gwright@…]

I'm reopening this bug sooner than expected. I have added variants that turn off all langauge bindings except tcl (which is required for DP to run anyway). The language bindings are enabled by the +guile, +ocaml, +perl, +php, +python and +ruby variants. To turn them all on, use the +all_lang variant.

This is done by some particularly ugly mucking in the Portfile, but this shoudl go away in the next release (2.7), which supports the standard --enable and --disable-feature arguments to configure.

-Greg

[gwright@…]

I forgot to mention that the java language bindings are not supported yet. (The configure script on my system does not detect Apple's java properly.) If someone needs this and can supply a patch, I will be happy to include it.

-Greg