Vendor dependencies

Let's see how I like this workflow.

vendor/procfs/Cargo.toml

@@ -0,0 +1,96 @@
+# THIS FILE IS AUTOMATICALLY GENERATED BY CARGO
+#
+# When uploading crates to the registry Cargo will automatically
+# "normalize" Cargo.toml files for maximal compatibility
+# with all versions of Cargo and also rewrite `path` dependencies
+# to registry (e.g., crates.io) dependencies.
+#
+# If you are reading this file be aware that the original Cargo.toml
+# will likely look very different (and much more reasonable).
+# See Cargo.toml.orig for the original contents.
+
+[package]
+edition = "2018"
+rust-version = "1.48"
+name = "procfs"
+version = "0.14.2"
+authors = ["Andrew Chin <achin@eminence32.net>"]
+description = "Interface to the linux procfs pseudo-filesystem"
+documentation = "https://docs.rs/procfs/"
+readme = "README.md"
+keywords = [
+    "procfs",
+    "proc",
+    "linux",
+    "process",
+]
+categories = [
+    "os::unix-apis",
+    "filesystem",
+]
+license = "MIT OR Apache-2.0"
+repository = "https://github.com/eminence/procfs"
+
+[package.metadata.docs.rs]
+all-features = true
+
+[[bench]]
+name = "cpuinfo"
+harness = false
+
+[dependencies.backtrace]
+version = "0.3"
+optional = true
+
+[dependencies.bitflags]
+version = "1.2"
+
+[dependencies.byteorder]
+version = "1.2.3"
+features = ["i128"]
+
+[dependencies.chrono]
+version = "0.4.20"
+features = ["clock"]
+optional = true
+default-features = false
+
+[dependencies.flate2]
+version = "1.0.3"
+optional = true
+
+[dependencies.hex]
+version = "0.4"
+
+[dependencies.lazy_static]
+version = "1.0.2"
+
+[dependencies.rustix]
+version = "0.36.0"
+features = [
+    "fs",
+    "process",
+    "param",
+    "thread",
+]
+
+[dependencies.serde]
+version = "1.0"
+features = ["derive"]
+optional = true
+
+[dev-dependencies.criterion]
+version = "0.3"
+
+[dev-dependencies.failure]
+version = "0.1"
+
+[dev-dependencies.procinfo]
+version = "0.4.2"
+
+[features]
+default = [
+    "chrono",
+    "flate2",
+]
+serde1 = ["serde"]