Reposting previously private discussion to the bug thread. Hi Jonas,
I have prepared the plugin changes and pushed them to my fork. Would you prefer to take a look there first, or should I go ahead and open an MR for review? Best, Junyong Liang On Tue, May 12, 2026 at 11:38 AM Smart SangGe <[email protected]> wrote: > Hi Jonas, > > I have prepared the plugin changes and pushed them to my fork. > > Would you prefer to take a look there first, or should I go ahead and open > an MR for review? > > Best, > Junyong Liang > > > On Thu, Apr 30, 2026, 18:42 Jonas Smedegaard <[email protected]> wrote: > >> Quoting Smart SangGe (2026-04-30 12:16:01) >> > First, I want to clarify that I have no intention of including >> Recommends >> > for any development toolchains or LSP daemons. My goal is to keep these >> > packages focused strictly on syntax highlighting. By naming them >> > hx-highlight-core and hx-highlight-extra, I hope to signal to users that >> > these are infrastructure for the editor's visual output, not a shortcut >> to >> > a full IDE setup. Since we are only dealing with Treesitter shared >> objects >> > and queries, the installation footprint will remain minimal, and the >> > "bloat" from external compilers or LSPs is not a factor here. >> >> Makes sense. >> >> We can later add metapackages on top of these, if needed. You are right >> that there is no need to complicate matters further here. >> >> > As for the versioning concern I raised earlier: if I bundle everything >> > under one source package, the build system should ensure that all >> parsers >> > are updated and released in lockstep with the editor version, which >> > effectively eliminates the risk of broken dependencies during release >> > windows. >> > >> > Does this consolidated "Core/Extra" plan sound like a more sustainable >> path >> > forward to you? >> >> The core/extra separation makes sense to me, yes. >> >> The versioning makes sense too, but there is one concern (which I don't >> think there is an easy answer to and is a general limitation of how we >> in Debian stuff multiple upstream packages together): When multiple >> upstream packages are lumped together, then we are mre likely to miss >> XZ-style security flaws on some of them. >> >> You are quite welcome to go ahead with your proposed plan. >> >> Thanks, >> >> - Jonas >> >> -- >> * Jonas Smedegaard - idealist & Internet-arkitekt >> * Tlf.: +45 40843136 Website: http://dr.jones.dk/ >> * Sponsorship: https://ko-fi.com/drjones >> >> [x] quote me freely [ ] ask before reusing [ ] keep private >> >
