Remove vendored dependencies

While it appears that by now we actually can get successful builds
without Cargo insisting on Internet access by virtue of using the
--frozen flag, maintaining vendored dependencies is somewhat of a pain
point. This state will also get worse with upcoming changes that replace
argparse in favor of structopt and pull in a slew of new dependencies by
doing so. Then there is also the repository structure aspect, which is
non-standard due to the way we vendor dependencies and a potential
source of confusion.
In order to fix these problems, this change removes all the vendored
dependencies we have.

Delete subrepo argparse/:argparse
Delete subrepo base32/:base32
Delete subrepo cc/:cc
Delete subrepo cfg-if/:cfg-if
Delete subrepo getrandom/:getrandom
Delete subrepo lazy-static/:lazy-static
Delete subrepo libc/:libc
Delete subrepo nitrokey-sys/:nitrokey-sys
Delete subrepo nitrokey/:nitrokey
Delete subrepo rand/:rand

1 files changed, 0 insertions, 28 deletions

diff --git a/rand/rand_jitter/tests/mod.rs b/rand/rand_jitter/tests/mod.rs
deleted file mode 100644
index 961dc27..0000000
--- a/rand/rand_jitter/tests/mod.rs
+++ /dev/null
@@ -1,28 +0,0 @@
-use rand_jitter::JitterRng;
-#[cfg(feature = "std")]
-use rand_core::RngCore;
-
-#[cfg(feature = "std")]
-#[test]
-fn test_jitter_init() {
-    // Because this is a debug build, measurements here are not representive
-    // of the final release build.
-    // Don't fail this test if initializing `JitterRng` fails because of a
-    // bad timer (the timer from the standard library may not have enough
-    // accuracy on all platforms).
-    match JitterRng::new() {
-        Ok(ref mut rng) => {
-            // false positives are possible, but extremely unlikely
-            assert!(rng.next_u32() | rng.next_u32() != 0);
-        },
-        Err(_) => {},
-    }
-}
-
-#[test]
-fn test_jitter_bad_timer() {
-    fn bad_timer() -> u64 { 0 }
-    let mut rng = JitterRng::new_with_timer(bad_timer);
-    assert!(rng.test_timer().is_err());
-}
-