2019-04-17 05:53:42 +00:00
|
|
|
# This file is automatically @generated by Cargo.
|
|
|
|
|
# It is not intended for manual editing.
|
2014-11-26 07:36:09 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "ansi_term"
|
2020-10-10 01:14:35 +00:00
|
|
|
version = "0.12.1"
|
2015-06-04 14:15:39 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 01:14:35 +00:00
|
|
|
checksum = "d52a9bb7ec0cf484c551830a7ce27bd20d67eac647e1befb56b0be4ee39a55d2"
|
2018-05-03 17:34:20 +00:00
|
|
|
dependencies = [
|
2020-10-10 01:14:35 +00:00
|
|
|
"winapi",
|
2018-05-03 17:34:20 +00:00
|
|
|
]
|
|
|
|
|
|
2019-07-14 10:55:30 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "autocfg"
|
2020-10-10 01:14:35 +00:00
|
|
|
version = "1.0.1"
|
2019-07-14 10:55:30 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 01:14:35 +00:00
|
|
|
checksum = "cdb031dd78e28731d87d56cc8ffef4a8f36ca26c38fe2de700543e627f8a464a"
|
2019-07-14 10:55:30 +00:00
|
|
|
|
2015-01-27 15:01:17 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "bitflags"
|
2020-10-10 01:14:35 +00:00
|
|
|
version = "1.2.1"
|
2015-01-27 15:01:17 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 01:14:35 +00:00
|
|
|
checksum = "cf1de2fe8c75bc145a2f577add951f8134889b4795d47466a54a5c846d691693"
|
2015-01-27 15:01:17 +00:00
|
|
|
|
2016-02-10 19:02:20 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "byteorder"
|
2020-10-10 01:14:35 +00:00
|
|
|
version = "1.3.4"
|
2016-02-10 19:02:20 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 01:14:35 +00:00
|
|
|
checksum = "08c48aae112d48ed9f069b33538ea9e3e90aa263cfa3d1c24309612b1f7472de"
|
2016-02-10 19:02:20 +00:00
|
|
|
|
2018-03-11 10:11:28 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "cc"
|
2020-10-10 01:14:35 +00:00
|
|
|
version = "1.0.61"
|
2018-03-11 10:11:28 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 01:14:35 +00:00
|
|
|
checksum = "ed67cbde08356238e75fc4656be4749481eeffb09e19f320a25237d5221c985d"
|
|
|
|
|
dependencies = [
|
|
|
|
|
"jobserver",
|
|
|
|
|
]
|
2018-03-11 10:11:28 +00:00
|
|
|
|
|
|
|
|
[[package]]
|
|
|
|
|
name = "cfg-if"
|
2020-10-10 01:14:35 +00:00
|
|
|
version = "0.1.10"
|
2018-03-11 10:11:28 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 01:14:35 +00:00
|
|
|
checksum = "4785bdd1c96b2a846b2bd7cc02e86b6b3dbf14e7e53446c4f54c92a361040822"
|
2018-03-11 10:11:28 +00:00
|
|
|
|
2015-06-04 14:15:39 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "datetime"
|
2021-04-01 15:58:01 +00:00
|
|
|
version = "0.5.2"
|
2015-06-05 02:04:56 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2021-04-01 15:58:01 +00:00
|
|
|
checksum = "44c3f7a77f3e57fedf80e09136f2d8777ebf621207306f6d96d610af048354bc"
|
2015-02-09 16:33:27 +00:00
|
|
|
dependencies = [
|
2020-10-10 00:56:36 +00:00
|
|
|
"libc",
|
|
|
|
|
"locale",
|
|
|
|
|
"pad",
|
|
|
|
|
"redox_syscall",
|
2020-10-10 01:14:35 +00:00
|
|
|
"winapi",
|
2015-02-09 16:33:27 +00:00
|
|
|
]
|
|
|
|
|
|
2018-01-31 06:46:46 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "exa"
|
2021-04-04 22:03:53 +00:00
|
|
|
version = "0.11.0-pre"
|
2018-01-31 06:46:46 +00:00
|
|
|
dependencies = [
|
2020-10-10 00:56:36 +00:00
|
|
|
"ansi_term",
|
|
|
|
|
"datetime",
|
|
|
|
|
"git2",
|
|
|
|
|
"glob",
|
|
|
|
|
"lazy_static",
|
|
|
|
|
"libc",
|
|
|
|
|
"locale",
|
|
|
|
|
"log",
|
|
|
|
|
"natord",
|
|
|
|
|
"num_cpus",
|
|
|
|
|
"number_prefix",
|
|
|
|
|
"scoped_threadpool",
|
|
|
|
|
"term_grid",
|
|
|
|
|
"term_size",
|
|
|
|
|
"unicode-width",
|
|
|
|
|
"users",
|
|
|
|
|
"zoneinfo_compiled",
|
2018-01-31 06:46:46 +00:00
|
|
|
]
|
|
|
|
|
|
2015-01-27 15:01:17 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "git2"
|
2020-10-10 01:14:35 +00:00
|
|
|
version = "0.13.11"
|
2015-10-01 23:56:39 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 01:14:35 +00:00
|
|
|
checksum = "1e094214efbc7fdbbdee952147e493b00e99a4e52817492277e98967ae918165"
|
2015-01-27 15:01:17 +00:00
|
|
|
dependencies = [
|
2020-10-10 00:56:36 +00:00
|
|
|
"bitflags",
|
|
|
|
|
"libc",
|
|
|
|
|
"libgit2-sys",
|
|
|
|
|
"log",
|
|
|
|
|
"openssl-sys",
|
|
|
|
|
"url",
|
2015-01-27 15:01:17 +00:00
|
|
|
]
|
|
|
|
|
|
2016-10-30 14:43:33 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "glob"
|
2019-04-17 05:53:42 +00:00
|
|
|
version = "0.3.0"
|
2016-10-30 14:43:33 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 00:56:36 +00:00
|
|
|
checksum = "9b919933a397b79c37e33b77bb2aa3dc8eb6e165ad809e58ff75bc7db2e34574"
|
2016-10-30 14:43:33 +00:00
|
|
|
|
2020-10-10 01:14:35 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "hermit-abi"
|
|
|
|
|
version = "0.1.17"
|
|
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
checksum = "5aca5565f760fb5b220e499d72710ed156fdb74e631659e99377d9ebfbd13ae8"
|
|
|
|
|
dependencies = [
|
|
|
|
|
"libc",
|
|
|
|
|
]
|
|
|
|
|
|
2016-02-10 15:22:43 +00:00
|
|
|
[[package]]
|
2017-03-30 19:23:14 +00:00
|
|
|
name = "idna"
|
2020-10-10 01:14:35 +00:00
|
|
|
version = "0.2.0"
|
2016-02-10 15:22:43 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 01:14:35 +00:00
|
|
|
checksum = "02e2673c30ee86b5b96a9cb52ad15718aa1f966f5ab9ad54a8b95d5ca33120a9"
|
2016-02-10 15:22:43 +00:00
|
|
|
dependencies = [
|
2020-10-10 00:56:36 +00:00
|
|
|
"matches",
|
|
|
|
|
"unicode-bidi",
|
|
|
|
|
"unicode-normalization",
|
2015-12-15 21:38:56 +00:00
|
|
|
]
|
|
|
|
|
|
2017-08-05 06:09:26 +00:00
|
|
|
[[package]]
|
2020-10-10 01:14:35 +00:00
|
|
|
name = "jobserver"
|
|
|
|
|
version = "0.1.21"
|
2017-08-05 06:09:26 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 01:14:35 +00:00
|
|
|
checksum = "5c71313ebb9439f74b00d9d2dcec36440beaf57a6aa0623068441dd7cd81a7f2"
|
2017-08-05 06:09:26 +00:00
|
|
|
dependencies = [
|
2020-10-10 01:14:35 +00:00
|
|
|
"libc",
|
2017-08-05 06:09:26 +00:00
|
|
|
]
|
|
|
|
|
|
2017-06-25 13:51:44 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "lazy_static"
|
2020-10-10 01:14:35 +00:00
|
|
|
version = "1.4.0"
|
2017-06-25 13:51:44 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 01:14:35 +00:00
|
|
|
checksum = "e2abad23fbc42b3700f2f279844dc832adb2b2eb069b2df918f455c4e18cc646"
|
2017-06-25 13:51:44 +00:00
|
|
|
|
2015-02-04 01:34:21 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "libc"
|
2020-10-10 01:14:35 +00:00
|
|
|
version = "0.2.79"
|
2015-11-04 17:01:05 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 01:14:35 +00:00
|
|
|
checksum = "2448f6066e80e3bfc792e9c98bf705b4b0fc6e8ef5b43e5889aff0eaa9c58743"
|
2015-11-04 17:01:05 +00:00
|
|
|
|
2015-01-27 15:01:17 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "libgit2-sys"
|
Use Specsheet for the extended tests
This commit changes the way the extended test suite is run.
Previously, there was a folder full of outputs, and a script that ran exa repeatedly to check the outputs match. This script was hacked-together, with many problems:
• It stops at the first failure, so if one test fails, you have no idea how many actually failed.
• It also didn't actually show you the diff if one was different, it just checked it.
• It combined stdout and stderr, and didn't test the exit status of exa.
• All the output file names were just whatever I felt like calling the file at the time.
• There is no way to only run a few of the tests — you have to run the whole thing each time.
• There's no feel-good overall view where you see how many tests are passing.
I started writing Specsheet to solve this problem (amongst other problems), and now, three and a half years later, it's finally ready for prime time.
The tests are now defined as data rather than as a script. The outputs have a consistent naming convention (directory_flags.ansitxt), and they check stdout, stderr, and exit status separately. Specsheet also lets simple outputs (empty, non-empty, or one-line error messages) can be written inline rather than needing to be in files.
So even though this pretty much runs the same tests as the run.sh script did, the tests are now more organised, making it easy to see where tests are missing and functionality is not being tested.
2020-10-17 19:39:44 +00:00
|
|
|
version = "0.12.14+1.1.0"
|
2015-10-01 23:56:39 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
Use Specsheet for the extended tests
This commit changes the way the extended test suite is run.
Previously, there was a folder full of outputs, and a script that ran exa repeatedly to check the outputs match. This script was hacked-together, with many problems:
• It stops at the first failure, so if one test fails, you have no idea how many actually failed.
• It also didn't actually show you the diff if one was different, it just checked it.
• It combined stdout and stderr, and didn't test the exit status of exa.
• All the output file names were just whatever I felt like calling the file at the time.
• There is no way to only run a few of the tests — you have to run the whole thing each time.
• There's no feel-good overall view where you see how many tests are passing.
I started writing Specsheet to solve this problem (amongst other problems), and now, three and a half years later, it's finally ready for prime time.
The tests are now defined as data rather than as a script. The outputs have a consistent naming convention (directory_flags.ansitxt), and they check stdout, stderr, and exit status separately. Specsheet also lets simple outputs (empty, non-empty, or one-line error messages) can be written inline rather than needing to be in files.
So even though this pretty much runs the same tests as the run.sh script did, the tests are now more organised, making it easy to see where tests are missing and functionality is not being tested.
2020-10-17 19:39:44 +00:00
|
|
|
checksum = "8f25af58e6495f7caf2919d08f212de550cfa3ed2f5e744988938ea292b9f549"
|
2015-01-27 15:01:17 +00:00
|
|
|
dependencies = [
|
2020-10-10 00:56:36 +00:00
|
|
|
"cc",
|
|
|
|
|
"libc",
|
|
|
|
|
"libz-sys",
|
|
|
|
|
"pkg-config",
|
2015-01-27 15:01:17 +00:00
|
|
|
]
|
|
|
|
|
|
|
|
|
|
[[package]]
|
|
|
|
|
name = "libz-sys"
|
2020-10-10 01:14:35 +00:00
|
|
|
version = "1.1.2"
|
2015-01-27 15:01:17 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 01:14:35 +00:00
|
|
|
checksum = "602113192b08db8f38796c4e85c39e960c145965140e918018bcde1952429655"
|
2015-01-27 15:01:17 +00:00
|
|
|
dependencies = [
|
2020-10-10 00:56:36 +00:00
|
|
|
"cc",
|
|
|
|
|
"libc",
|
|
|
|
|
"pkg-config",
|
|
|
|
|
"vcpkg",
|
2015-01-27 15:01:17 +00:00
|
|
|
]
|
|
|
|
|
|
2015-02-10 16:08:10 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "locale"
|
2017-06-11 08:34:02 +00:00
|
|
|
version = "0.2.2"
|
2015-02-10 16:08:10 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 00:56:36 +00:00
|
|
|
checksum = "5fdbe492a9c0238da900a1165c42fc5067161ce292678a6fe80921f30fe307fd"
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
dependencies = [
|
2020-10-10 00:56:36 +00:00
|
|
|
"libc",
|
2017-08-04 02:17:11 +00:00
|
|
|
]
|
|
|
|
|
|
2017-08-19 09:06:07 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "log"
|
2020-10-10 01:14:35 +00:00
|
|
|
version = "0.4.11"
|
2017-08-19 09:06:07 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 01:14:35 +00:00
|
|
|
checksum = "4fabed175da42fed1fa0746b0ea71f412aa9d35e76e95e59b192c64b9dc2bf8b"
|
2018-03-11 10:11:28 +00:00
|
|
|
dependencies = [
|
2020-10-10 00:56:36 +00:00
|
|
|
"cfg-if",
|
2018-03-11 10:11:28 +00:00
|
|
|
]
|
2017-08-19 09:06:07 +00:00
|
|
|
|
2015-01-27 15:01:17 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "matches"
|
2019-04-17 05:53:42 +00:00
|
|
|
version = "0.1.8"
|
2015-01-27 15:01:17 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 00:56:36 +00:00
|
|
|
checksum = "7ffc5c5338469d4d3ea17d269fa8ea3512ad247247c30bd2df69e68309ed0a08"
|
2015-01-27 15:01:17 +00:00
|
|
|
|
2015-06-21 11:52:53 +00:00
|
|
|
[[package]]
|
2016-02-10 15:22:43 +00:00
|
|
|
name = "natord"
|
|
|
|
|
version = "1.0.9"
|
2015-06-21 11:52:53 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 00:56:36 +00:00
|
|
|
checksum = "308d96db8debc727c3fd9744aac51751243420e46edf401010908da7f8d5e57c"
|
2015-06-21 11:52:53 +00:00
|
|
|
|
2015-04-03 22:14:49 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "num_cpus"
|
2020-10-10 01:14:35 +00:00
|
|
|
version = "1.13.0"
|
2015-04-03 22:14:49 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 01:14:35 +00:00
|
|
|
checksum = "05499f3756671c15885fee9034446956fff3f243d6077b91e5767df161f766b3"
|
2015-04-03 22:14:49 +00:00
|
|
|
dependencies = [
|
2020-10-10 01:14:35 +00:00
|
|
|
"hermit-abi",
|
2020-10-10 00:56:36 +00:00
|
|
|
"libc",
|
2015-04-03 22:14:49 +00:00
|
|
|
]
|
|
|
|
|
|
2014-12-18 07:00:31 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "number_prefix"
|
2020-10-10 01:14:35 +00:00
|
|
|
version = "0.4.0"
|
2015-01-12 00:20:28 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 01:14:35 +00:00
|
|
|
checksum = "830b246a0e5f20af87141b25c173cd1b609bd7779a4617d6ec582abaf90870f3"
|
2014-12-18 07:00:31 +00:00
|
|
|
|
2019-01-06 11:37:43 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "openssl-src"
|
Use Specsheet for the extended tests
This commit changes the way the extended test suite is run.
Previously, there was a folder full of outputs, and a script that ran exa repeatedly to check the outputs match. This script was hacked-together, with many problems:
• It stops at the first failure, so if one test fails, you have no idea how many actually failed.
• It also didn't actually show you the diff if one was different, it just checked it.
• It combined stdout and stderr, and didn't test the exit status of exa.
• All the output file names were just whatever I felt like calling the file at the time.
• There is no way to only run a few of the tests — you have to run the whole thing each time.
• There's no feel-good overall view where you see how many tests are passing.
I started writing Specsheet to solve this problem (amongst other problems), and now, three and a half years later, it's finally ready for prime time.
The tests are now defined as data rather than as a script. The outputs have a consistent naming convention (directory_flags.ansitxt), and they check stdout, stderr, and exit status separately. Specsheet also lets simple outputs (empty, non-empty, or one-line error messages) can be written inline rather than needing to be in files.
So even though this pretty much runs the same tests as the run.sh script did, the tests are now more organised, making it easy to see where tests are missing and functionality is not being tested.
2020-10-17 19:39:44 +00:00
|
|
|
version = "111.12.0+1.1.1h"
|
2019-01-06 11:37:43 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
Use Specsheet for the extended tests
This commit changes the way the extended test suite is run.
Previously, there was a folder full of outputs, and a script that ran exa repeatedly to check the outputs match. This script was hacked-together, with many problems:
• It stops at the first failure, so if one test fails, you have no idea how many actually failed.
• It also didn't actually show you the diff if one was different, it just checked it.
• It combined stdout and stderr, and didn't test the exit status of exa.
• All the output file names were just whatever I felt like calling the file at the time.
• There is no way to only run a few of the tests — you have to run the whole thing each time.
• There's no feel-good overall view where you see how many tests are passing.
I started writing Specsheet to solve this problem (amongst other problems), and now, three and a half years later, it's finally ready for prime time.
The tests are now defined as data rather than as a script. The outputs have a consistent naming convention (directory_flags.ansitxt), and they check stdout, stderr, and exit status separately. Specsheet also lets simple outputs (empty, non-empty, or one-line error messages) can be written inline rather than needing to be in files.
So even though this pretty much runs the same tests as the run.sh script did, the tests are now more organised, making it easy to see where tests are missing and functionality is not being tested.
2020-10-17 19:39:44 +00:00
|
|
|
checksum = "858a4132194f8570a7ee9eb8629e85b23cbc4565f2d4a162e87556e5956abf61"
|
2019-01-06 11:37:43 +00:00
|
|
|
dependencies = [
|
2020-10-10 00:56:36 +00:00
|
|
|
"cc",
|
2019-01-06 11:37:43 +00:00
|
|
|
]
|
|
|
|
|
|
|
|
|
|
[[package]]
|
|
|
|
|
name = "openssl-sys"
|
2020-10-10 01:14:35 +00:00
|
|
|
version = "0.9.58"
|
2019-01-06 11:37:43 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 01:14:35 +00:00
|
|
|
checksum = "a842db4709b604f0fe5d1170ae3565899be2ad3d9cbc72dedc789ac0511f78de"
|
2019-01-06 11:37:43 +00:00
|
|
|
dependencies = [
|
2020-10-10 00:56:36 +00:00
|
|
|
"autocfg",
|
|
|
|
|
"cc",
|
|
|
|
|
"libc",
|
|
|
|
|
"openssl-src",
|
|
|
|
|
"pkg-config",
|
|
|
|
|
"vcpkg",
|
2019-01-06 11:37:43 +00:00
|
|
|
]
|
|
|
|
|
|
2015-02-09 16:33:27 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "pad"
|
2020-10-10 01:14:35 +00:00
|
|
|
version = "0.1.6"
|
2015-02-09 16:33:27 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 01:14:35 +00:00
|
|
|
checksum = "d2ad9b889f1b12e0b9ee24db044b5129150d5eada288edc800f789928dc8c0e3"
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
dependencies = [
|
2020-10-10 00:56:36 +00:00
|
|
|
"unicode-width",
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
]
|
2015-02-09 16:33:27 +00:00
|
|
|
|
2017-06-25 13:51:44 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "percent-encoding"
|
2020-10-10 01:14:35 +00:00
|
|
|
version = "2.1.0"
|
2017-06-25 13:51:44 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 01:14:35 +00:00
|
|
|
checksum = "d4fd5641d01c8f18a23da7b6fe29298ff4b55afcccdf78973b24cf3175fee32e"
|
2017-06-25 13:51:44 +00:00
|
|
|
|
2015-01-27 15:01:17 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "pkg-config"
|
Use Specsheet for the extended tests
This commit changes the way the extended test suite is run.
Previously, there was a folder full of outputs, and a script that ran exa repeatedly to check the outputs match. This script was hacked-together, with many problems:
• It stops at the first failure, so if one test fails, you have no idea how many actually failed.
• It also didn't actually show you the diff if one was different, it just checked it.
• It combined stdout and stderr, and didn't test the exit status of exa.
• All the output file names were just whatever I felt like calling the file at the time.
• There is no way to only run a few of the tests — you have to run the whole thing each time.
• There's no feel-good overall view where you see how many tests are passing.
I started writing Specsheet to solve this problem (amongst other problems), and now, three and a half years later, it's finally ready for prime time.
The tests are now defined as data rather than as a script. The outputs have a consistent naming convention (directory_flags.ansitxt), and they check stdout, stderr, and exit status separately. Specsheet also lets simple outputs (empty, non-empty, or one-line error messages) can be written inline rather than needing to be in files.
So even though this pretty much runs the same tests as the run.sh script did, the tests are now more organised, making it easy to see where tests are missing and functionality is not being tested.
2020-10-17 19:39:44 +00:00
|
|
|
version = "0.3.19"
|
2015-02-09 16:33:27 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
Use Specsheet for the extended tests
This commit changes the way the extended test suite is run.
Previously, there was a folder full of outputs, and a script that ran exa repeatedly to check the outputs match. This script was hacked-together, with many problems:
• It stops at the first failure, so if one test fails, you have no idea how many actually failed.
• It also didn't actually show you the diff if one was different, it just checked it.
• It combined stdout and stderr, and didn't test the exit status of exa.
• All the output file names were just whatever I felt like calling the file at the time.
• There is no way to only run a few of the tests — you have to run the whole thing each time.
• There's no feel-good overall view where you see how many tests are passing.
I started writing Specsheet to solve this problem (amongst other problems), and now, three and a half years later, it's finally ready for prime time.
The tests are now defined as data rather than as a script. The outputs have a consistent naming convention (directory_flags.ansitxt), and they check stdout, stderr, and exit status separately. Specsheet also lets simple outputs (empty, non-empty, or one-line error messages) can be written inline rather than needing to be in files.
So even though this pretty much runs the same tests as the run.sh script did, the tests are now more organised, making it easy to see where tests are missing and functionality is not being tested.
2020-10-17 19:39:44 +00:00
|
|
|
checksum = "3831453b3449ceb48b6d9c7ad7c96d5ea673e9b470a1dc578c2ce6521230884c"
|
2015-02-09 16:33:27 +00:00
|
|
|
|
2017-09-30 07:48:04 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "redox_syscall"
|
2020-10-10 01:14:35 +00:00
|
|
|
version = "0.1.57"
|
2018-05-03 17:34:20 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 01:14:35 +00:00
|
|
|
checksum = "41cc0f7e4d5d4544e8861606a285bb08d3e70712ccc7d2b84d7c0ccfaf4b05ce"
|
2018-05-03 17:34:20 +00:00
|
|
|
|
Parallelise the details view!
This commit removes the threadpool in `main.rs` that stats each command-line argument separately, and replaces it with a *scoped* threadpool in `options/details.rs` that builds the table in parallel! Running this on my machine halves the execution time when tree-ing my entire home directory (which isn't exactly a common occurrence, but it's the only way to give exa a large running time)
The statting will be added back in parallel at a later stage. This was facilitated by the previous changes to recursion that made it easier to deal with.
There's a lot of large sweeping architectural changes. Here's a smattering of them:
- In `main.rs`, the files are now passed around as vectors of files rather than array slices of files. This is because `File`s aren't `Clone`, and the `Vec` is necessary to give away ownership of the files at the appropriate point.
- In the details view, files are now sorted *all* the time, rather than obeying the command-line order. As they're run in parallel, they have no guaranteed order anyway, so we *have* to sort them again. (I'm not sure if this should be the intended behaviour or not!) This means that the `Details` struct has to have the filter *all* the time, not only while recursing, so it's been moved out of the `recurse` field.
- We use `scoped_threadpool` over `threadpool`, a recent addition. It's only safely used on Nightly, which we're using anyway, so that's OK!
- Removed a bunch of out-of-date comments.
This also fixes #77, mainly by accident :)
2015-09-02 22:19:10 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "scoped_threadpool"
|
2018-03-11 10:11:28 +00:00
|
|
|
version = "0.1.9"
|
Parallelise the details view!
This commit removes the threadpool in `main.rs` that stats each command-line argument separately, and replaces it with a *scoped* threadpool in `options/details.rs` that builds the table in parallel! Running this on my machine halves the execution time when tree-ing my entire home directory (which isn't exactly a common occurrence, but it's the only way to give exa a large running time)
The statting will be added back in parallel at a later stage. This was facilitated by the previous changes to recursion that made it easier to deal with.
There's a lot of large sweeping architectural changes. Here's a smattering of them:
- In `main.rs`, the files are now passed around as vectors of files rather than array slices of files. This is because `File`s aren't `Clone`, and the `Vec` is necessary to give away ownership of the files at the appropriate point.
- In the details view, files are now sorted *all* the time, rather than obeying the command-line order. As they're run in parallel, they have no guaranteed order anyway, so we *have* to sort them again. (I'm not sure if this should be the intended behaviour or not!) This means that the `Details` struct has to have the filter *all* the time, not only while recursing, so it's been moved out of the `recurse` field.
- We use `scoped_threadpool` over `threadpool`, a recent addition. It's only safely used on Nightly, which we're using anyway, so that's OK!
- Removed a bunch of out-of-date comments.
This also fixes #77, mainly by accident :)
2015-09-02 22:19:10 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 00:56:36 +00:00
|
|
|
checksum = "1d51f5df5af43ab3f1360b429fa5e0152ac5ce8c0bd6485cae490332e96846a8"
|
Parallelise the details view!
This commit removes the threadpool in `main.rs` that stats each command-line argument separately, and replaces it with a *scoped* threadpool in `options/details.rs` that builds the table in parallel! Running this on my machine halves the execution time when tree-ing my entire home directory (which isn't exactly a common occurrence, but it's the only way to give exa a large running time)
The statting will be added back in parallel at a later stage. This was facilitated by the previous changes to recursion that made it easier to deal with.
There's a lot of large sweeping architectural changes. Here's a smattering of them:
- In `main.rs`, the files are now passed around as vectors of files rather than array slices of files. This is because `File`s aren't `Clone`, and the `Vec` is necessary to give away ownership of the files at the appropriate point.
- In the details view, files are now sorted *all* the time, rather than obeying the command-line order. As they're run in parallel, they have no guaranteed order anyway, so we *have* to sort them again. (I'm not sure if this should be the intended behaviour or not!) This means that the `Details` struct has to have the filter *all* the time, not only while recursing, so it's been moved out of the `recurse` field.
- We use `scoped_threadpool` over `threadpool`, a recent addition. It's only safely used on Nightly, which we're using anyway, so that's OK!
- Removed a bunch of out-of-date comments.
This also fixes #77, mainly by accident :)
2015-09-02 22:19:10 +00:00
|
|
|
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
[[package]]
|
2017-03-30 19:23:14 +00:00
|
|
|
name = "term_grid"
|
2018-03-11 10:11:28 +00:00
|
|
|
version = "0.1.7"
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 00:56:36 +00:00
|
|
|
checksum = "230d3e804faaed5a39b08319efb797783df2fd9671b39b7596490cb486d702cf"
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
dependencies = [
|
2020-10-10 00:56:36 +00:00
|
|
|
"unicode-width",
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
]
|
|
|
|
|
|
2017-08-05 06:09:26 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "term_size"
|
2020-10-10 01:14:35 +00:00
|
|
|
version = "0.3.2"
|
2017-08-05 06:09:26 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 01:14:35 +00:00
|
|
|
checksum = "1e4129646ca0ed8f45d09b929036bafad5377103edd06e50bf574b353d2b08d9"
|
2017-08-05 06:09:26 +00:00
|
|
|
dependencies = [
|
2020-10-10 00:56:36 +00:00
|
|
|
"libc",
|
2020-10-10 01:14:35 +00:00
|
|
|
"winapi",
|
2017-08-05 06:09:26 +00:00
|
|
|
]
|
|
|
|
|
|
2020-10-10 01:14:35 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "tinyvec"
|
|
|
|
|
version = "0.3.4"
|
|
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
checksum = "238ce071d267c5710f9d31451efec16c5ee22de34df17cc05e56cbc92e967117"
|
|
|
|
|
|
2015-06-23 09:54:57 +00:00
|
|
|
[[package]]
|
2017-03-30 19:23:14 +00:00
|
|
|
name = "unicode-bidi"
|
2017-08-04 02:17:11 +00:00
|
|
|
version = "0.3.4"
|
2015-06-23 09:54:57 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 00:56:36 +00:00
|
|
|
checksum = "49f2bd0c6468a8230e1db229cff8029217cf623c767ea5d60bfbd42729ea54d5"
|
2015-06-23 09:54:57 +00:00
|
|
|
dependencies = [
|
2020-10-10 00:56:36 +00:00
|
|
|
"matches",
|
2015-06-23 09:54:57 +00:00
|
|
|
]
|
|
|
|
|
|
2017-03-30 19:23:14 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "unicode-normalization"
|
2020-10-10 01:14:35 +00:00
|
|
|
version = "0.1.13"
|
2017-03-30 19:23:14 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 01:14:35 +00:00
|
|
|
checksum = "6fb19cf769fa8c6a80a162df694621ebeb4dafb606470b2b2fce0be40a98a977"
|
2019-04-17 05:53:42 +00:00
|
|
|
dependencies = [
|
2020-10-10 01:14:35 +00:00
|
|
|
"tinyvec",
|
2019-04-17 05:53:42 +00:00
|
|
|
]
|
2017-03-30 19:23:14 +00:00
|
|
|
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "unicode-width"
|
2020-10-10 01:14:35 +00:00
|
|
|
version = "0.1.8"
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 01:14:35 +00:00
|
|
|
checksum = "9337591893a19b88d8d87f2cec1e73fad5cdfd10e5a6f349f498ad6ea2ffb1e3"
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
|
2015-01-27 15:01:17 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "url"
|
2020-10-10 01:14:35 +00:00
|
|
|
version = "2.1.1"
|
2015-01-27 15:01:17 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 01:14:35 +00:00
|
|
|
checksum = "829d4a8476c35c9bf0bbce5a3b23f4106f79728039b726d292bb93bc106787cb"
|
2015-01-27 15:01:17 +00:00
|
|
|
dependencies = [
|
2020-10-10 00:56:36 +00:00
|
|
|
"idna",
|
|
|
|
|
"matches",
|
|
|
|
|
"percent-encoding",
|
2015-01-27 15:01:17 +00:00
|
|
|
]
|
|
|
|
|
|
2014-12-12 11:17:55 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "users"
|
2020-10-10 01:01:12 +00:00
|
|
|
version = "0.11.0"
|
2015-01-12 00:20:28 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 01:01:12 +00:00
|
|
|
checksum = "24cc0f6d6f267b73e5a2cadf007ba8f9bc39c6a6f9666f8cf25ea809a153b032"
|
2015-02-04 01:34:21 +00:00
|
|
|
dependencies = [
|
2020-10-10 00:56:36 +00:00
|
|
|
"libc",
|
|
|
|
|
"log",
|
2015-02-04 01:34:21 +00:00
|
|
|
]
|
2014-12-12 11:17:55 +00:00
|
|
|
|
2017-06-25 13:51:44 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "vcpkg"
|
2020-10-10 01:14:35 +00:00
|
|
|
version = "0.2.10"
|
2017-11-21 06:31:37 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 01:14:35 +00:00
|
|
|
checksum = "6454029bf181f092ad1b853286f23e2c507d8e8194d01d92da4a55c274a5508c"
|
2017-11-21 06:31:37 +00:00
|
|
|
|
2017-08-05 06:09:26 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "winapi"
|
2020-10-10 01:14:35 +00:00
|
|
|
version = "0.3.9"
|
2017-08-05 06:09:26 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 01:14:35 +00:00
|
|
|
checksum = "5c839a674fcd7a98952e593242ea400abe93992746761e38641405d28b00f419"
|
2018-05-03 17:34:20 +00:00
|
|
|
dependencies = [
|
2020-10-10 00:56:36 +00:00
|
|
|
"winapi-i686-pc-windows-gnu",
|
|
|
|
|
"winapi-x86_64-pc-windows-gnu",
|
2018-05-03 17:34:20 +00:00
|
|
|
]
|
|
|
|
|
|
|
|
|
|
[[package]]
|
|
|
|
|
name = "winapi-i686-pc-windows-gnu"
|
|
|
|
|
version = "0.4.0"
|
|
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 00:56:36 +00:00
|
|
|
checksum = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
|
2018-05-03 17:34:20 +00:00
|
|
|
|
|
|
|
|
[[package]]
|
|
|
|
|
name = "winapi-x86_64-pc-windows-gnu"
|
|
|
|
|
version = "0.4.0"
|
|
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2020-10-10 00:56:36 +00:00
|
|
|
checksum = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
|
2018-05-03 17:34:20 +00:00
|
|
|
|
2016-02-10 19:02:20 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "zoneinfo_compiled"
|
2021-04-01 15:58:01 +00:00
|
|
|
version = "0.5.1"
|
2017-09-30 07:48:04 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2021-04-01 15:58:01 +00:00
|
|
|
checksum = "64fbebe65e899530f43bd760b23fda8f141118f4db49952b02998cbd0907a5de"
|
2016-02-10 19:02:20 +00:00
|
|
|
dependencies = [
|
2020-10-10 00:56:36 +00:00
|
|
|
"byteorder",
|
|
|
|
|
"datetime",
|
|
|
|
|
]
|
