On Mon, 2024 Aug 12 15:21-04:00, Jeremy Bícha wrote: > > No, they don't. There definitely are several C libraries that do > include a static library in Debian, but most of the C libraries I > maintain do not.
Of the 57 lib*-dev libraries that chromium lists in its Build-Deps, all of which appear to be C/C++ libraries, 19 do not have lib*.a libraries. And only two are of concern with my builds (harfbuzz and dav1d). > It's going to be a bit painful to try to use a newer/different system > library than provided by the system if you're not going to use a > sandboxed approach. However, it sounds like you figured out a working > solution. Yes; my solution was to work around the missing static library, and report the issue to Debian so that it can be fixed. > Hopefully, you don't need to maintain support for older distros for > very long. How long is jammy being supported? As long as I don't have to provide half the world as build deps, that would be the ideal. > In this case, it's not that you need a new library; it's that Debian > didn't enable the subset feature earlier. Sorry about that. It's all the same from my perspective... > Sorry, I don't see enough demand for harfbuzz to be distributed as a > static library for me to make that change in the Debian packaging at > this time. What kind of quorum are you looking for? It's not like this package gets much in the way of bug reports in general, after all. I think I've made a reasonable case for including a static build. (If you want to argue that this package is complex enough that adding a static build is a fair amount of work, then that's a different story, of course.) --Daniel
