> got only fixed in the latest 1.10 release which was released 1 month ago and > probably isn't part of many distributions yet
Yeah, it would be a while before distros support that version. > Is there some policy preventing this? I don't know Debian policies, too complex, don't care. My concern was from another project that I was reading, that was blocked because it included source for a library that was available on Debian. I am afraid I don't remember if the source had changes, if they were accepted upstream or not, and what the final solution was, I stopped following it since it all seemed too hard. Neither Scintilla nor ctags libraries appear to be in the Debian repository (at least not in Linux Debian), so included source is fine. > But would it be OK for Debian to fall back to the bundled version in this > case? Debian expert advice somebody please? But I would think it would be acceptable, you still need the source for Win and Mac, and so if the build only builds the source instead of depending on the library on Win, Mac, and Linux distros with library less that 1.10 or whatever version. This information should be clearly documented so that Debian and other packagers understand it is temporary until they have a suitable library version. I presume `jsonrpc-glib` needs to use the matching version of `json-glib` and that is why its source is included too. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/pull/1331#issuecomment-2440225476 You are receiving this because you are subscribed to this thread. Message ID: <geany/geany-plugins/pull/1331/c2440225...@github.com>
