3 ms·
Use a single version of the arrow library, and build everything against that one. I don't see where the problem is. I don't use Rust or third-party build or pa
by mgaunard 2y ago
Use a single version of the arrow library, and build everything against that one. I don't see where the problem is.
I don't use Rust or third-party build or packaging systems -- I usually recommend that people don't do so either, but I understand that cargo is part of the appeal of Rust.
I'd say just build whatever you need to do, this way you won't be limited by arbitrary restrictions others have decided.
- hinkley 2y agoSecurity patches say no, doesn’t work that way.
- progval 2y agoI can't always do that because dependency A depends dependency B that depends on arrow 52, and dependency C depends on arrow 53. And sure, I can soft-fork dependency B to add support for arrow 53, and dependency A to depend on my soft-fork of dependency B, but it quickly becomes messy. Especially when in parallel I send unrelated patches to A and/or B.
- mgaunard 2y agoyour problem is caring about what other people have decided. Surely metadata is irrelevant and can be changed/overridden. You onboard a version and make sure everything you need can build against it, patching software as needed.