No description
Find a file
2013-12-27 17:01:55 -05:00
base64 Use same crate_id form as other utils 2013-12-27 17:01:55 -05:00
cat link -> crate_id, link is deprecated 2013-12-26 13:55:54 -05:00
dirname link -> crate_id, link is deprecated 2013-12-26 13:55:54 -05:00
echo link -> crate_id, link is deprecated 2013-12-26 13:55:54 -05:00
env link -> crate_id, link is deprecated 2013-12-26 13:55:54 -05:00
false link -> crate_id, link is deprecated 2013-12-26 13:55:54 -05:00
printenv link -> crate_id, link is deprecated 2013-12-26 13:55:54 -05:00
pwd link -> crate_id, link is deprecated 2013-12-26 13:55:54 -05:00
rmdir link -> crate_id, link is deprecated 2013-12-26 13:55:54 -05:00
true link -> crate_id, link is deprecated 2013-12-26 13:55:54 -05:00
wc link -> crate_id, link is deprecated 2013-12-26 13:55:54 -05:00
whoami link -> crate_id, link is deprecated 2013-12-26 13:55:54 -05:00
yes link -> crate_id, link is deprecated 2013-12-26 13:55:54 -05:00
.gitignore Add the first four utils 2013-08-02 19:33:31 +02:00
.travis.yml Fix travis 2013-10-22 16:18:22 +02:00
LICENSE Add the first four utils 2013-08-02 19:33:31 +02:00
Makefile Implement base64, resolves issue #42 2013-12-20 14:34:45 -05:00
README.md Implement base64, resolves issue #42 2013-12-20 14:34:45 -05:00

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, abandonned, 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.

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:

  1. Open an issue named "Implement [the utility of your choice]", e.g. "Implement ls"
  2. State that you are working on this utility.
  3. Develop the utility.
  4. 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

  • basename
  • chcon
  • chgrp
  • chmod
  • chown-core
  • chown
  • chroot
  • cksum
  • comm
  • copy
  • cp-hash
  • cp
  • csplit
  • cut
  • date
  • dd
  • df
  • dircolors
  • du
  • expand
  • expr
  • extent-scan
  • factor
  • find-mount-point
  • fmt
  • fold
  • getlimits
  • group-list
  • groups
  • head ( in progress )
  • hostid
  • hostname (in progress)
  • id
  • install
  • join
  • kill
  • lbracket
  • libstdbuf
  • link
  • ln
  • logname
  • ls-dir
  • ls-ls
  • ls-vdir
  • ls
  • make-prime-list
  • md5sum
  • mkdir
  • mkfifo
  • mknod
  • mktemp
  • mv
  • nice
  • nl
  • nohup
  • nproc
  • numfmt
  • od
  • operand2sig
  • paste
  • pathchk
  • pinky
  • pr
  • printf
  • prog-fprintf
  • ptx
  • readlink
  • realpath
  • relpath
  • remove
  • rm
  • runcon
  • seq
  • setuidgid
  • shred
  • shuf
  • sleep
  • sort
  • split
  • stat
  • stdbuf
  • stty
  • sum
  • sync
  • tac-pipe
  • tac
  • tail
  • tee
  • test
  • timeout
  • touch
  • tr
  • truncate
  • tsort
  • tty
  • uname-arch
  • uname-uname
  • uname
  • unexpand
  • uniq (in progress)
  • unlink
  • uptime
  • users
  • who

License

uutils are licensed under the MIT License - see the LICENSE file for details