Conversation
jarkko

Jarkko Sakkinen

Edited 4 hours ago
Through dependency graph GItoxide has a RSVM requirement of 1.88.

For me that means exactly to never use Gitoxide and stick using libgit2 bindings because they retain software ubiquitos across environment and toolchains.

This also thought me an important lesson: using well established C-library throught bindings is 9/10 times a better choice than using equivalent "pure Rust" implementation. This does not mean that the Rust implementation would be somehow"worse", generally it just seems that Rust developers are completely ignorant of optimizing things like RSVM.

That leaves you two options.

1. Use a really old version of "pure Rust" library in order to maintain RSVM of your choice. Usually this means using a version, which never will be updated.
2. Use Rust-bindings of a C-library and have always up to date version of the dependency while retaining RSVM of your choice.

The crazy RSVM requirement of Gitoxide zeros down its applicability for anything production. I will never touch it again.

#rustlang
1
0
0
epage@hachyderm.io

Ed Page

Reply to @jarkko

@jarkko Most of this might be obvious to you but for some readers, they may walk away with the wrong impression.

`gix`s MSRV (the acronym generally used in the ecosystem) for the latest version is 1.82. As you mentioned, the latest version of some dependencies may be higher. The MSRV-aware resolver can help select versions compatible with your tool chain. You don't have to update your MSRV to use it, just your development version.

Whether those transitive deps is a problem or not is dependent on which dependencies they are and their role in your application. Presumably, you'll eventually update your MSRV and get those newer versions, so it is not likey you'll never see them. And updating your toolchain is one mitigation option. An important question in all of this is your motivation for your MSRV as that will dictate your willingness to update your toolchain to get newer features, either from Rust or your dependencies.

When contemplating not getting updates when using an old toolchain, remember you are using an old, unsupported dependency, your toolchain.

0
0
0
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: