Comment # 10 on bug 1190288 from Yifan Jiang

(In reply to Dominique Leuenberger from comment #9)
> For reference: https://github.com/harfbuzz/harfbuzz/issues/3216
> 
> Harfbuzz 3.0 broke ABI and upstream has no interest in fixing this.
> 
> So Either stick to harfbuzz 2.9.x or make sure that all consumers of
> harfbuzz-subset.so.0 are being rebuilt

hmm, the ABI change can be also problematic for SLE/Leap build model, where the
old SP's binary of an inherited package is taken directly for the developing
release.

But I have a question regarding the upstream bug, the API change was happening
all they way of harfbuzz (who has never changed the so version for a decade),
why it becomes a major problem today from 2.9.x to 3.x.x?