|
|
||
|---|---|---|
| base64 | ||
| basename | ||
| cat | ||
| common | ||
| cp | ||
| dirname | ||
| du | ||
| echo | ||
| env | ||
| false | ||
| fold | ||
| groups | ||
| head | ||
| hostid | ||
| hostname | ||
| id | ||
| kill | ||
| logname | ||
| md5sum | ||
| mkdir | ||
| paste | ||
| printenv | ||
| pwd | ||
| rm | ||
| rmdir | ||
| seq | ||
| sleep | ||
| tac | ||
| tee | ||
| true | ||
| truncate | ||
| tty | ||
| uname | ||
| uptime | ||
| users | ||
| wc | ||
| whoami | ||
| yes | ||
| .gitignore | ||
| .gitmodules | ||
| .travis.yml | ||
| common.mk | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
uutils coreutils 
uutils is an attempt at writing universal (as in cross-platform) CLI utils in Rust. This repo is to aggregate the GNU coreutils rewrites.
Why?
Many GNU, Linux and other utils are pretty awesome, and obviously some effort has been spent in the past to port them to Windows. However, those projects are either old, abandoned, hosted on CVS, written in platform-specific C, etc.
Rust provides a good, platform-agnostic way of writing systems utils that are easy to compile anywhere, and this is as good a way as any to try and learn it.
Build Instructions
To simply build all available utilities:
make
To build all but a few of the available utilities:
make DONT_BUILD='UTILITY_1 UTILITY_2'
To build only a few of the available utilities:
make BUILD='UTILITY_1 UTILITY_2'
Test Instructions
To simply test all available utilities:
make test
To test all but a few of the available utilities:
make DONT_TEST='UTILITY_1 UTILITY_2' test
To test only a few of the available utilities:
make TEST='UTILITY_1 UTILITY_2' test
Contribute
Contributions are very welcome, and should target Rust's master branch until Rust 1.0 is released. You may claim an item on the to-do list by following these steps:
- Open an issue named "Implement [the utility of your choice]", e.g. "Implement ls"
- State that you are working on this utility.
- Develop the utility.
- Submit a pull request and close the issue. Your pull request should include deleting the utility from the to-do list on this README.
The steps above imply that, before starting to work on a utility, you should search the issues to make sure no one else is working on it.
To do
- chcon
- chgrp
- chmod
- chown-core
- chown
- chroot
- cksum
- comm
- copy
- cp-hash
- cp (some work done in
devbranch) - csplit
- cut
- date
- dd
- df
- dircolors
- expand (in progress)
- expr
- extent-scan
- factor
- find-mount-point
- fmt
- getlimits
- group-list
- install
- join
- lbracket
- libstdbuf
- link
- ln
- ls-dir
- ls-ls
- ls-vdir
- ls
- make-prime-list
- mkfifo
- mknod
- mktemp
- mv
- nice
- nl
- nohup
- nproc
- numfmt
- od
- operand2sig
- pathchk
- pinky
- pr
- printf
- prog-fprintf
- ptx
- readlink
- realpath
- relpath
- remove
- runcon
- setuidgid
- shred
- shuf
- sort
- split
- stat
- stdbuf
- stty (in progress)
- sum
- sync
- tac-pipe
- tail
- test
- timeout
- touch
- tr
- tsort
- uname-arch
- uname-uname
- unexpand
- uniq (in progress)
- unlink
- who
License
uutils is licensed under the MIT License - see the LICENSE file for details