harfbuzz doesn't use graphite2

[ryandesign (Ryan Carsten Schmidt)]

In harfbuzz 0.9.18 a new build system was introduced, and icu and graphite2 support, which had previously defaulted to on, now default to off. The NEWS file says:

Overview of changes leading to 0.9.18
Tuesday, May 28, 2013
=====================================

New build system:

- All unneeded code is all disabled by default,

- Uniscribe and CoreText shapers can be enabled with their --with options,

- icu_le and old shapers cannot be enabled for now,

- glib, freetype, and cairo will be detected automatically.
  They can be force on/off'ed with their --with options,

- icu and graphite2 are default off, can be enabled with their --with
  options,

Moreover, ICU support is now build into a separate library:
libharfbuzz-icu.so, and a new harfbuzz-icu.pc is shipped for it.
Distros can enable ICU now without every application on earth
getting linked to via libharfbuzz.so.

For distros I recommend that they make sure they are building --with-glib
--with-freetype --with-cairo, --with-icu, and optionally --with-graphite2;
And package harfbuzz and harfbuzz-icu separately.

In particular note the recommendation in the last line to package harfbuzz-icu separately. I'll see if I can make that into a separate subport.

[ryandesign (Ryan Carsten Schmidt)]

Hmm, contrary to the statement in the NEWS file, icu is still autodetected.

[ryandesign (Ryan Carsten Schmidt)]

r107441

[cooljeanius (Eric Gallager)]

I think the deactivate hack will need to be used:

x ./opt/local/include/hb-icu.h
Error: org.macports.activate for port harfbuzz-icu returned: Image error: /opt/local/lib/libharfbuzz-icu.0.dylib is being used by the active harfbuzz port.  Please deactivate this port first, or use 'port -f activate harfbuzz-icu' to force the activation.
DEBUG: Error code: registry::image-error

[ryandesign (Ryan Carsten Schmidt)]

The only way you should experience that problem when installing harfbuzz-icu with the -p flag is if harfbuzz failed to build. Did it? If so please file a bug report about that.