publishing a forked library with opinionated patches without changing internal crate names.

This page summarizes the projects mentioned and recommended in the original post on /r/rust

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
  • crates.io

    The Rust package registry

  • This has a few limitations ofcourse, so what I really want to do is publish my fork with my patches ( and other peoples patches ) to crates.io under a different name, and I want the end result for users being to only have to change the name in their Cargo.toml files in this manner:

  • semver-trick

    How to avoid complicated coordinated upgrades

  • The semver issue might be possible to mitigate using the semver trick, but at that point it's probably simpler to just get your patches merged upstream.

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts