This repository has been archived by the owner on Apr 18, 2019. It is now read-only.
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
First pass refresh of
hab
CLI UI with musl/libc fix.
hab CLI ------- This change is part spike and experiment and part functional. It is a first attempt at unifying the `hab` CLI output and formatting to be more consisten and easier to scan as a newcomer (in the short term) and experienced user (in the long term). Most of the commands have the following narrative, much like an essay: * An intro/goal/summary of the objective * A middle with the concrete steps to achieve the objective * A final summary/conclusion to confirm success Here is an example of a package install invocation: ``` > hab install core/redis » Installing core/redis ↓ Downloading core/glibc/2.22/20160427193532 16.21 MB / 16.21 MB \ [========================================] 100.00 % 2.98 MB/s ✓ Installed core/glibc/2.22/20160427193532 ↓ Downloading core/linux-headers/4.3/20160427193435 798.63 KB / 798.63 KB | [======================================] 100.00 % 1.56 MB/s ✓ Installed core/linux-headers/4.3/20160427193435 ↓ Downloading core/redis/3.0.7/20160427222845 1.46 MB / 1.46 MB | [==========================================] 100.00 % 3.28 MB/s ✓ Installed core/redis/3.0.7/20160427222845 ★ Install of core/redis complete with 3 packages installed. ``` musl/libc/ioctl --------------- In the course of building in a progress bar, an issue was found with in the `libc` crate relating to the types of ioctl contants when used by musl (more detail in: rust-lang/libc#289). Unfortunately, this meant vendoring libc so that it would be used as a transitive dependency in the crates that generated the errors (currently this is the `pbr` crate, which is completely correct in tits implementation). Without this temporary measure, the `hab` CLI won't build as-is with the musl target. The other option is to feature-disable the progress bar until the upstream is resolved, but it really hampers the far superior user experience that a progress bar like this provides. Signed-off-by: Fletcher Nichol <fnichol@nichol.ca> Pull request: #522 Approved by: fnichol
- Loading branch information