Declare env_logger as dependency only in the top level crate

The correct way to use the env_logger crate is to only depend on it the toplevel
aplication crate. In other crates we should just use the `log` crate facade
(which we already do).

Drop the env_logger dependency from all of our internal crates, and just keep it
in the the `libkrun` crate.

Signed-off-by: Matej Hrica <[email protected]>

Author: mtjhrc

Cargo.lock

@@ -17,7 +17,6 @@ virgl_resource_map2 = []
 [dependencies]
 bitflags = "1.2.0"
 crossbeam-channel = ">=0.5.15"
-env_logger = "0.9.0"
 libc = ">=0.2.39"
 libloading = "0.8"
 log = "0.4.0"

src/devices/Cargo.toml

@@ -8,6 +8,5 @@ edition = "2021"
 crossbeam-channel = ">=0.5.15"
 libloading = "0.8"
 log = "0.4.0"
-env_logger = "0.9.0"
 
 arch = { path = "../arch" }

src/hvf/Cargo.toml

@@ -6,7 +6,6 @@ edition = "2021"
 
 [dependencies]
 bitflags = "1.2.0"
-env_logger = "0.9.0"
 libc = ">=0.2.85"
 log = "0.4.0"
 vmm-sys-util = "0.12.1"

src/utils/Cargo.toml

@@ -15,7 +15,6 @@ snd = []
 
 [dependencies]
 crossbeam-channel = ">=0.5.15"
-env_logger = "0.9.0"
 flate2 = "1.0.35"
 libc = ">=0.2.39"
 linux-loader = { version = "0.13.0", features = ["bzimage", "elf", "pe"] }