On Feb 20, 2015, at 5:34 PM, René J.V. Bertin wrote: > On Friday February 20 2015 09:31:28 Daniel J. Luke wrote: > >> if possible/reasonable, a good solution here is to break the port in >> question up into two ports (one which installs the 'boostrap' version and >> one which installs the extra pieces that the variant would have installed). > > Sadly that isn't feasible, other than by patching the binary library :-/ > It should however be possible to remove the dependency on harfbuzz, and let > the configure script figure out whether it's there (or, if that doesn't work, > do a `file exists libharfbuzz` to determine whether the support can be > activated).
Ports should not build differently based on what other ports are already installed. Port builds should be repeatable and predictable. _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
