ryan77627/guix
1
0
Fork 0
mirror of https://git.in.rschanz.org/ryan77627/guix.git synced 2024-12-29 07:42:23 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

gnu: Remove rust-progrs-0.1.

Browse source 
* gnu/packages/crates-io.scm (rust-progrs-0.1): Delete variable.
This commit is contained in:
Efraim Flashner 2022-10-18 22:44:04 +03:00
parent 6549d6af2b
commit c9d9db88da
No known key found for this signature in database
GPG key ID: 41AAE7DCCA3D8351
1 changed files with 0 additions and 32 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

32
gnu/packages/crates-io.scm
View file

@ -44473,38 +44473,6 @@ (define-public rust-progressing-3
progress-bars for Rust.")
(license license:asl2.0)))
(define-public rust-progrs-0.1
(package
(name "rust-progrs")
(version "0.1.1")
(source
(origin
(method url-fetch)
(uri (crate-uri "progrs" version))
(file-name
(string-append name "-" version ".tar.gz"))
(sha256
(base32
"108jx8jrv2r1brhvbqfw6fwx298k5fnw3m46kn7lv0jx2wmf0ifz"))))
(build-system cargo-build-system)
(arguments '(#:tests? #f))
(home-page "https://nest.pijul.com/laumann/progrs")
(synopsis "Small library for displaying compact progress bars")
(description
"There are a number of libraries out there that can be used for progress
display, but in the author's opinion these libraries do it almost right -
either they eat up too much screen real estate (by not sticking to one line
per thing that should use progress) or they try to align stuff left and right.
In the author's humble opinion, the best example of just the right amount of
information vs screen real-estate is in the Git progress output (when cloning,
pulling, etc). It uses one line per thing, and may display both percentage
complete (in cases where it's known) and even throughput (for network
transfer).
This library mimics the Git way of showing progress.")
(license license:gpl2+)))
(define-public rust-proptest-1
(package
(name "rust-proptest")