2014-11-26 07:36:09 +00:00
|
|
|
[root]
|
|
|
|
|
name = "exa"
|
2015-03-02 14:54:38 +00:00
|
|
|
version = "0.2.0"
|
2014-11-26 07:36:09 +00:00
|
|
|
dependencies = [
|
2015-05-29 10:33:27 +00:00
|
|
|
"ansi_term 0.5.2",
|
2015-02-21 22:59:38 +00:00
|
|
|
"bitflags 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-05-03 10:47:25 +00:00
|
|
|
"datetime 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-05-29 10:33:27 +00:00
|
|
|
"getopts 0.2.11 (registry+https://github.com/rust-lang/crates.io-index)",
|
|
|
|
|
"git2 0.2.11 (git+https://github.com/alexcrichton/git2-rs.git)",
|
|
|
|
|
"libc 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
|
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
|
|
|
"locale 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-03-12 03:13:15 +00:00
|
|
|
"natord 1.0.8 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-05-09 22:57:18 +00:00
|
|
|
"num_cpus 0.2.5 (registry+https://github.com/rust-lang/crates.io-index)",
|
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
|
|
|
"number_prefix 0.2.4 (registry+https://github.com/rust-lang/crates.io-index)",
|
|
|
|
|
"pad 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-04-23 12:46:37 +00:00
|
|
|
"unicode-width 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-05-06 20:46:21 +00:00
|
|
|
"users 0.4.1 (registry+https://github.com/rust-lang/crates.io-index)",
|
2014-11-26 07:36:09 +00:00
|
|
|
]
|
|
|
|
|
|
|
|
|
|
[[package]]
|
|
|
|
|
name = "ansi_term"
|
2015-05-09 22:57:18 +00:00
|
|
|
version = "0.5.2"
|
2014-11-26 07:36:09 +00:00
|
|
|
|
2015-01-27 15:01:17 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "bitflags"
|
2015-02-09 19:40:49 +00:00
|
|
|
version = "0.1.1"
|
2015-01-27 15:01:17 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
|
2015-02-09 16:33:27 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "datetime"
|
2015-05-03 10:47:25 +00:00
|
|
|
version = "0.1.7"
|
2015-02-09 19:40:49 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2015-02-09 16:33:27 +00:00
|
|
|
dependencies = [
|
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
|
|
|
"locale 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-05-03 10:47:25 +00:00
|
|
|
"num 0.1.24 (registry+https://github.com/rust-lang/crates.io-index)",
|
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
|
|
|
"pad 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-05-03 10:47:25 +00:00
|
|
|
"regex 0.1.30 (registry+https://github.com/rust-lang/crates.io-index)",
|
|
|
|
|
"regex_macros 0.1.17 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-02-09 16:33:27 +00:00
|
|
|
]
|
|
|
|
|
|
|
|
|
|
[[package]]
|
|
|
|
|
name = "gcc"
|
2015-05-03 11:46:05 +00:00
|
|
|
version = "0.3.5"
|
2015-02-09 16:33:27 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
|
2015-01-12 00:31:24 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "getopts"
|
2015-05-29 10:33:27 +00:00
|
|
|
version = "0.2.11"
|
2015-01-12 00:31:24 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2015-02-04 01:34:21 +00:00
|
|
|
dependencies = [
|
2015-04-03 22:14:49 +00:00
|
|
|
"log 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-02-04 01:34:21 +00:00
|
|
|
]
|
2015-01-12 00:31:24 +00:00
|
|
|
|
2015-01-27 15:01:17 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "git2"
|
2015-05-29 10:33:27 +00:00
|
|
|
version = "0.2.11"
|
|
|
|
|
source = "git+https://github.com/alexcrichton/git2-rs.git#49c7a7b3853626180e1767051ed53f0400140ff2"
|
2015-01-27 15:01:17 +00:00
|
|
|
dependencies = [
|
2015-02-09 19:40:49 +00:00
|
|
|
"bitflags 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-05-29 10:33:27 +00:00
|
|
|
"libc 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
|
|
|
|
|
"libgit2-sys 0.2.14 (git+https://github.com/alexcrichton/git2-rs.git)",
|
2015-05-16 12:17:50 +00:00
|
|
|
"url 0.2.34 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-01-27 15:01:17 +00:00
|
|
|
]
|
|
|
|
|
|
2015-02-04 01:34:21 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "libc"
|
2015-05-29 10:33:27 +00:00
|
|
|
version = "0.1.8"
|
2015-02-04 01:34:21 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
|
2015-01-27 15:01:17 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "libgit2-sys"
|
2015-05-29 10:33:27 +00:00
|
|
|
version = "0.2.14"
|
|
|
|
|
source = "git+https://github.com/alexcrichton/git2-rs.git#49c7a7b3853626180e1767051ed53f0400140ff2"
|
2015-01-27 15:01:17 +00:00
|
|
|
dependencies = [
|
2015-05-29 10:33:27 +00:00
|
|
|
"libc 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
|
|
|
|
|
"libssh2-sys 0.1.23 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-05-03 10:47:25 +00:00
|
|
|
"libz-sys 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-05-03 11:46:05 +00:00
|
|
|
"openssl-sys 0.6.2 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-05-06 20:46:21 +00:00
|
|
|
"pkg-config 0.3.4 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-01-27 15:01:17 +00:00
|
|
|
]
|
|
|
|
|
|
|
|
|
|
[[package]]
|
|
|
|
|
name = "libressl-pnacl-sys"
|
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
|
|
|
version = "2.1.5"
|
2015-01-27 15:01:17 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
dependencies = [
|
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
|
|
|
"pnacl-build-helper 1.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-01-27 15:01:17 +00:00
|
|
|
]
|
|
|
|
|
|
|
|
|
|
[[package]]
|
|
|
|
|
name = "libssh2-sys"
|
2015-05-29 10:33:27 +00:00
|
|
|
version = "0.1.23"
|
2015-01-27 15:01:17 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
dependencies = [
|
2015-05-29 10:33:27 +00:00
|
|
|
"libc 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-05-03 10:47:25 +00:00
|
|
|
"libz-sys 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-05-03 11:46:05 +00:00
|
|
|
"openssl-sys 0.6.2 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-05-06 20:46:21 +00:00
|
|
|
"pkg-config 0.3.4 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-01-27 15:01:17 +00:00
|
|
|
]
|
|
|
|
|
|
|
|
|
|
[[package]]
|
|
|
|
|
name = "libz-sys"
|
2015-05-03 10:47:25 +00:00
|
|
|
version = "0.1.3"
|
2015-01-27 15:01:17 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
dependencies = [
|
2015-05-29 10:33:27 +00:00
|
|
|
"libc 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-05-06 20:46:21 +00:00
|
|
|
"pkg-config 0.3.4 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-01-27 15:01:17 +00:00
|
|
|
]
|
|
|
|
|
|
2015-02-10 16:08:10 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "locale"
|
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
|
|
|
version = "0.1.8"
|
2015-02-10 16:08:10 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
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 = [
|
2015-05-29 10:33:27 +00:00
|
|
|
"libc 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-05-03 10:47:25 +00:00
|
|
|
"num 0.1.24 (registry+https://github.com/rust-lang/crates.io-index)",
|
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-10 16:08:10 +00:00
|
|
|
|
2015-02-04 01:34:21 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "log"
|
2015-04-03 22:14:49 +00:00
|
|
|
version = "0.3.1"
|
2015-02-04 01:34:21 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2015-04-03 22:14:49 +00:00
|
|
|
dependencies = [
|
2015-05-29 10:33:27 +00:00
|
|
|
"libc 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-04-03 22:14:49 +00:00
|
|
|
]
|
2015-02-04 01:34:21 +00:00
|
|
|
|
2015-01-27 15:01:17 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "matches"
|
|
|
|
|
version = "0.1.2"
|
|
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
|
2014-12-12 11:26:18 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "natord"
|
2015-03-12 03:13:15 +00:00
|
|
|
version = "1.0.8"
|
2015-01-12 00:20:28 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2014-12-12 11:26:18 +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 = "num"
|
2015-05-03 10:47:25 +00:00
|
|
|
version = "0.1.24"
|
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"
|
|
|
|
|
dependencies = [
|
2015-05-03 10:47:25 +00:00
|
|
|
"rand 0.3.8 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-05-03 11:46:05 +00:00
|
|
|
"rustc-serialize 0.3.14 (registry+https://github.com/rust-lang/crates.io-index)",
|
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-04-03 22:14:49 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "num_cpus"
|
2015-05-09 22:57:18 +00:00
|
|
|
version = "0.2.5"
|
2015-04-03 22:14:49 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
dependencies = [
|
2015-05-29 10:33:27 +00:00
|
|
|
"libc 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-04-03 22:14:49 +00:00
|
|
|
]
|
|
|
|
|
|
2014-12-18 07:00:31 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "number_prefix"
|
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
|
|
|
version = "0.2.4"
|
2015-01-12 00:20:28 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
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 = [
|
2015-05-03 10:47:25 +00:00
|
|
|
"num 0.1.24 (registry+https://github.com/rust-lang/crates.io-index)",
|
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
|
|
|
]
|
2014-12-18 07:00:31 +00:00
|
|
|
|
2015-01-27 15:01:17 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "openssl-sys"
|
2015-05-03 11:46:05 +00:00
|
|
|
version = "0.6.2"
|
2015-01-27 15:01:17 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
dependencies = [
|
2015-05-03 11:46:05 +00:00
|
|
|
"gcc 0.3.5 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-05-29 10:33:27 +00:00
|
|
|
"libc 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
|
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
|
|
|
"libressl-pnacl-sys 2.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-05-06 20:46:21 +00:00
|
|
|
"pkg-config 0.3.4 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-01-27 15:01:17 +00:00
|
|
|
]
|
|
|
|
|
|
2015-02-09 16:33:27 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "pad"
|
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
|
|
|
version = "0.1.4"
|
2015-02-09 16:33:27 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
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 = [
|
|
|
|
|
"unicode-width 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
|
|
|
|
|
]
|
2015-02-09 16:33:27 +00:00
|
|
|
|
2015-01-27 15:01:17 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "pkg-config"
|
2015-05-06 20:46:21 +00:00
|
|
|
version = "0.3.4"
|
2015-02-09 16:33:27 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
|
2015-01-27 15:01:17 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "pnacl-build-helper"
|
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
|
|
|
version = "1.4.0"
|
2015-01-27 15:01:17 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
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 = [
|
|
|
|
|
"tempdir 0.3.4 (registry+https://github.com/rust-lang/crates.io-index)",
|
|
|
|
|
]
|
|
|
|
|
|
|
|
|
|
[[package]]
|
|
|
|
|
name = "rand"
|
2015-05-03 10:47:25 +00:00
|
|
|
version = "0.3.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"
|
|
|
|
|
dependencies = [
|
2015-05-29 10:33:27 +00:00
|
|
|
"libc 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
|
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
|
|
|
|
2015-01-05 14:41:43 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "regex"
|
2015-05-03 10:47:25 +00:00
|
|
|
version = "0.1.30"
|
2015-01-05 14:41:43 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
|
|
|
|
|
[[package]]
|
|
|
|
|
name = "regex_macros"
|
2015-05-03 10:47:25 +00:00
|
|
|
version = "0.1.17"
|
2015-01-05 14:41:43 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
dependencies = [
|
2015-05-03 10:47:25 +00:00
|
|
|
"regex 0.1.30 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-01-05 14:41:43 +00:00
|
|
|
]
|
|
|
|
|
|
2015-01-27 15:01:17 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "rustc-serialize"
|
2015-05-03 11:46:05 +00:00
|
|
|
version = "0.3.14"
|
2015-01-27 15:01:17 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
|
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 = "tempdir"
|
|
|
|
|
version = "0.3.4"
|
|
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
dependencies = [
|
2015-05-03 10:47:25 +00:00
|
|
|
"rand 0.3.8 (registry+https://github.com/rust-lang/crates.io-index)",
|
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"
|
|
|
|
|
version = "0.1.1"
|
|
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
|
2015-01-27 15:01:17 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "url"
|
2015-05-16 12:17:50 +00:00
|
|
|
version = "0.2.34"
|
2015-01-27 15:01:17 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
dependencies = [
|
|
|
|
|
"matches 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-05-03 11:46:05 +00:00
|
|
|
"rustc-serialize 0.3.14 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-01-27 15:01:17 +00:00
|
|
|
]
|
|
|
|
|
|
2014-12-12 11:17:55 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "users"
|
2015-05-06 20:46:21 +00:00
|
|
|
version = "0.4.1"
|
2015-01-12 00:20:28 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2015-02-04 01:34:21 +00:00
|
|
|
dependencies = [
|
2015-05-29 10:33:27 +00:00
|
|
|
"libc 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-02-04 01:34:21 +00:00
|
|
|
]
|
2014-12-12 11:17:55 +00:00
|
|
|
|
