py26-matplotlib 0.99.0 - Set CocoaAgg backend as variant

[mdippery@…]

py26-matplotlib automatically builds with the CocoaAgg backend, which requires a large number of dependencies related to the PyObjC bridge, which aren't necessary if you're doing basic work with py26-matplotlib and don't want to use the CocoaAgg backend at all. In keeping with the port's convention, this patch creates a variant, "cocoa", that enables the CocoaAgg backend.

This patch also removes py26-configobj as a dependency, since it does not seem to be an actual dependency in this version of matplotlib.

[ram@…]

Just removing the dependencies is not really sufficient as if cocoa bindings are installed the CocoaAgg backend will be built regardless of whether the cocoa variant is specified or not, the building of the the cocoa backend will need to be disabled unless the variant is specified. This is done for the other backend variants and it also needs to be done for the cocoa backend if it is going to be made a variant. See the various patches that are applied.

[mdippery@…]

Are the Objective-C bridge dependencies necessary, then? I built and ran matplotlib without them, using the patch to the Portfile as given above.

[ram@…]

Only if you want the CocoaAgg backend. But my point is that if you have py26-cocoa, and friends, installed the CocoaAgg backend will be built regardless of whether the cocoa variant is specified. Therefore if you then remove the cocoa bindings port will not complain as they are not marked as dependencies for matplotlib but then the CocoaAgg backend will not longer function as the bindings will have been removed. If you want the CocoaAgg backend to be a variant then it needs to be disabled like the other interactive backends are.

[mdippery@…]

A new version of the Portfile with changes from comments incorporated

[mdippery@…]

A patch file for the existing patch-setup.cfg.diff. Should be applied to files/patch-setup.cfg.diff

[mdippery@…]

A replacement for the existing patch-disable_optional_deps.diff

[ram@…]

Thanks, I'll take a look at these. Initially they look OK.

[ram@…]

Looking at patch-setup.diff , this disables the MacOSX backend not the CocoaAgg backend. The reason the CocoaAgg backend is on by default is that I haven't found a way to disable it.

[ram@…]

Can't find a way to disable CocoaAgg backend.