On Oct 28, 2016, at 07:33, Richard Hipp <d...@sqlite.org> wrote: > > Perhaps true. But in my brief look at Rust I observed that you really > cannot use it effectively without also having to use Git. The two > seem closely linked. Is that incorrect?
It is indeed. Sadly, the examples don't help to dispel that at all. Git is merely a first-class citizen for some of the tooling (like Cargo[0]), and if you dig deeply enough, you'll notice things like `--hg` flags and explicit mentions in, e.g., Cargo.toml of the version control system being used to pull in dependencies for those who choose to have that tool manage their checkouts for them. (Though, in my experience, some of the features are a little schizophrenic in their raisons d'être, and the proliferation of language-specific package managers is proving to be an acquired taste like IPAs or caviar. YMMV.) However, there's also the option of referring to dependencies in Cargo by a file path on the local filesystem tree, relative to where that particular crate's (the Rustese word for package) Cargo.toml resides. There's more at [1]. If you're willing to roll your own crate by hand, you can even use something like Darcs, as the thrussh portable SSH library[2] does. The only other consequence outside of that is that you lose some of the ability for Cargo to manage your dependencies for you if you choose to rely on one that doesn't use Git and wish to use something other than a published stable version. Given Cargo's opinions about version numbers[3] though, I don't think that's such a bad consequence. —n 0: http://crates.io/ 1: http://doc.crates.io/specifying-dependencies.html 2: https://pijul.org/thrussh/ 3: http://doc.crates.io/manifest.html#the-version-field _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
