Since https://bugs.openjdk.java.net/browse/JDK-8249821, libharfbuzz is a separate library, available in the JDK libs directory.
With https://bugs.openjdk.java.net/browse/JDK-8250894 it is possible for distributors to bundle their own libharfbuzz.

However, there is another usecase: a developer creates a (C) application, and wants to link it with the Java libs and with a bunch of system libs, e.g. libpango, libharfbuzz...
Typically, the java lib directory would be provided to the linker via `-L/path/to/jdk/libs`
Since that directory also contains libharfbuzz, that one would be used for linking as well. However, many Linux libraries depend at runtime on the system provided libharfbuzz.so (/usr/lib/...) , which can be a different version, resulting in crashes.

It seems to me that if the JDK bundles and re-distribute libharfbuzz, that this might better be done using a different name, so that the linker is not unintentionally including this library.