Mirrors/coreutils
2
0
Fork 0
mirror of https://github.com/uutils/coreutils synced 2024-11-15 01:17:09 +00:00
Code Issues Projects Releases Packages Wiki Activity
No description
69 commits 14 branches 26 tags 47 MiB
Rust 98.1%
Shell 1.3%
Batchfile 0.2%
Makefile 0.2%
Python 0.1%
Find a file
Heather 2aa7e552f7 init -> new (reverted in rust) 
from_utf8_slice -> from_utf8
2013-12-06 09:31:49 +04:00
cat init -> new (reverted in rust) 2013-12-06 09:31:49 +04:00
dirname init -> new (reverted in rust) 2013-12-06 09:31:49 +04:00
echo rust println supports multi-line ... 2013-12-03 16:56:15 +04:00
env Fix build. 2013-11-28 00:14:19 +01:00
false Add the first four utils 2013-08-02 19:33:31 +02:00
printenv std::rt::io -> std::io 2013-11-13 12:17:41 +01:00
pwd simple pwd implementation 2013-12-05 16:44:43 +04:00
true Add the first four utils 2013-08-02 19:33:31 +02:00
wc init -> new (reverted in rust) 2013-12-06 09:31:49 +04:00
whoami Fix build. 2013-11-28 00:14:19 +01:00
yes std::rt::io -> std::io 2013-11-13 12:17:41 +01: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 simple pwd implementation 2013-12-05 16:44:43 +04:00
README.md simple pwd implementation 2013-12-05 16:44:43 +04:00

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

  • base64
  • 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
  • hostid
  • hostname
  • 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
  • rmdir
  • 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