Dear #OpenSource community,
And now it is on us to give something back.
Feel free to use/share/improve it, we will continue to publish more of our work over time.
Thank you for your support.
@senfcall Thanks, that's great news. I was hoping you would share your insights and knowledge like this - and here it is! 👍
@senfcall Have you considered uploading senfi to crates.io?
That way, people could list it in their Cargo.toml files without having to provide a path to your git repository, and it could be installed just with `cargo install senfi`.
Hi @wizzwizz4, unfortunately, crates.io uses Microsoft's Github for authentication, and thus requires an account there to upload crates. For reasons explained on the page linked above, we want to avoid that for now.
As you said, cargo supports specifying git dependencies (down to commit hashes: https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#specifying-dependencies-from-git-repositories). You can also use cargo install with the locally cloned repo ("cargo install --path ."). For easier deployment, we internally use "cargo deb" to create debian packages.
@senfcall Oops; forgot about that requirement! Have you thought about running your own registry? https://doc.rust-lang.org/cargo/reference/registries.html
@wizzwizz4 Since we use cargo-deb and an internal debian repository for distributing our software internally, we haven't felt the need to create one. Would there be any advantage over just having the gitlab public as it is? If I understand correctly, using a custom registry would require more configuration inside Cargo.toml, and in addition we would need to set up and maintain the registry itself. Does depending on a git commit hash pose a problem for your use case?
chaos.social – a Fediverse instance for & by the Chaos community