2026-03-31 15:34 UTC
Replies (3)
-
@sgued@pouet.chapril.org 2026-03-31 15:40
@ekuber@hachyderm.io How would go for C dependencies that are meant to be statically linked and not really packaged ? Asking seriously as a maintainer of the littlefs2-sys crate used in bare-metal embedded, I wish we had a better option that just having it as a git submodule.
-
@piecritic@hachyderm.io 2026-03-31 15:45
@ekuber@hachyderm.io I disagree. I care a lot more about portability of binaries than the other tradeoffs. That said, I do not vendor the C/C++ code, it's almost always a git subtree or submodule depending on use case. The reason is that I put a great deal of effort into making sure that the library builds for all desktop and mobile operating systems statically (which is a fun surgical operation for Windows half the time). In the case where it's sensible to allow using the system library, that's an env var opt-in. To put this discussion differently: I think that cargo doesn't cater for this use case particularly well and there's an open design space here that could satisfy both of our views without conflicting with either. :D
-
@michalfita@mastodon.social 2026-04-01 17:59
@ekuber@hachyderm.io This is Catch 22 with where the trade off is going. Correct dependency on system libraries is usually target dependent, often even distro dependent - can maintainer afford the cost of keeping the compatibility? Or can deliver library that works on all? There's certain advantage with `cargo` as installed packages manager (could be better aligned to that), as it allow to keep tool installed outside the system scope. It's my preferred way, but you have to learn to live with that.