Hi Jonas,
I have tested a split prototype locally.
The |hx| source package now builds |hx-plugin-dev|, which contains
|languages.toml|, |runtime/queries|, and the |hx-plugin-abi| helper.
Using that package as an additional local build dependency, a separate
|hx-grammars| source package can successfully build both
|hx-highlight-core| and |hx-highlight-extra| in sbuild.
The package builds themselves are succeeding. The remaining issues are
primarily Lintian warnings in the prototype |hx-grammars| source
package, mostly because |debian/copyright| still needs to be reduced and
normalized to reflect the split source tree.
I have not created a Salsa repository yet, as I do not want to preempt
your preferred maintenance layout. Would you prefer that I create a
proposed |hx-grammars| repository on Salsa for review, or would you
rather I keep the prototype as a branch or patch series for the time being?
Best regards,
Junyong Liang
On 2026/6/4 19:05, Jonas Smedegaard wrote:
I think I understand your point now: the motivation for splitting is not
reducing coupling, but isolating maintenance and release risks from the
core hx package.
Let me take a closer look at the uwsgi-style ABI approach you mentioned
and see how a split package would look in practice.
Thanks for considering!
- Jonas
