midfavila/sbase
1
0
Fork 0
Code Issues Pull Requests Projects Releases 1 Wiki Activity
0bb5f5f453
sbase/README

119 lines
5.6 KiB
Plaintext
Raw Normal View History

Add initial README
2014-02-12 09:34:09 -05:00
sbase - suckless unix tools
===========================
sbase is a collection of unix tools that are inherently portable
across UNIX and UNIX-like systems.
Add column to mark UTF-8 support One major milestone is to have the sbase-tools supporting UTF-8. Tools like cut(1) with the -n flag don't make sense otherwise. And while the gnu coreutils cut(1) blatantly ignores such an important aspect, we will not tolerate this madness and mark it as a TODO in the main README. Since most tools inherently support UTF-8 anyway, this just concerns tools which mangle with text or search in it in special ways.
2015-01-18 13:36:13 -05:00
The following tools are implemented ('*' == finished, '#' == UTF-8 support,
'=' == implicit UTF-8 support):
Add an easier to edit "table" of tools in README We need to go through the tools and update this table to reflect current state.
2014-11-20 18:01:56 -05:00
Also indent the headings
2015-01-18 13:41:14 -05:00
UTILITY POSIX 2008 COMPLIANT MISSING OPTIONS
------- -------------------- ---------------
Add column to mark UTF-8 support One major milestone is to have the sbase-tools supporting UTF-8. Tools like cut(1) with the -n flag don't make sense otherwise. And while the gnu coreutils cut(1) blatantly ignores such an important aspect, we will not tolerate this madness and mark it as a TODO in the main README. Since most tools inherently support UTF-8 anyway, this just concerns tools which mangle with text or search in it in special ways.
2015-01-18 13:36:13 -05:00
=* basename yes none
=* cal yes none
=* cat yes none
= chgrp no -h, -H, -L, -P
=* chmod yes none
= chown no -h, -H, -L, -P
= chroot non-posix none
=* cksum yes none
Mark non-UTF8-tools as non-finished This makes clearer that these tools might require some more work.
2015-01-23 17:00:20 -05:00
cmp yes none
cols non-posix none
Add column to mark UTF-8 support One major milestone is to have the sbase-tools supporting UTF-8. Tools like cut(1) with the -n flag don't make sense otherwise. And while the gnu coreutils cut(1) blatantly ignores such an important aspect, we will not tolerate this madness and mark it as a TODO in the main README. Since most tools inherently support UTF-8 anyway, this just concerns tools which mangle with text or search in it in special ways.
2015-01-18 13:36:13 -05:00
=* comm yes none
Mark insane POSIX flags which we are not planning to include into sbase. What's left to discuss is how we're going to handle them in the tools (dump usage() or silently ignore them).
2015-01-23 17:31:46 -05:00
= cp no -H, (-i), -L
Add column to mark UTF-8 support One major milestone is to have the sbase-tools supporting UTF-8. Tools like cut(1) with the -n flag don't make sense otherwise. And while the gnu coreutils cut(1) blatantly ignores such an important aspect, we will not tolerate this madness and mark it as a TODO in the main README. Since most tools inherently support UTF-8 anyway, this just concerns tools which mangle with text or search in it in special ways.
2015-01-18 13:36:13 -05:00
=* cron non-posix none
Add UTF-8-delimiter-support to cut(1) Now you can specify a multibyte-delimiter to cut, which should definitely be possible for the end-user (Fuck POSIX). Looking at GNU/coreutils' cut(1)[0], which basically ignores the difference between characters and bytes, the -n-option and which is bloated as hell, one has to wonder why they are still default. This is insane! Things like this personally keep me motivated to make sbase better every day. [0]: http://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=blob;f=src/cut.c;hb=HEAD NSFW! You have been warned.
2015-01-22 06:32:50 -05:00
#* cut yes none
Add mandoc-manpage for date(1) and clean up code and mark it as finished in README.
2015-01-23 16:54:25 -05:00
=* date yes none
Add mandoc-manpage for dirname(1) and mark it as finished in the README.
2015-01-23 17:17:54 -05:00
=* dirname yes none
Mark insane POSIX flags which we are not planning to include into sbase. What's left to discuss is how we're going to handle them in the tools (dump usage() or silently ignore them).
2015-01-23 17:31:46 -05:00
= du no -H, -L, (-x)
Add mandoc-manpage for echo(1) and mark it as finished in the README.
2015-01-23 17:49:24 -05:00
=* echo yes none
Add mandoc-manpage for env(1) and mark it as finished in the README.
2015-01-23 18:22:06 -05:00
=* env yes none
Add tablist support and a mandoc-manpage to expand(1) and mark it as finished in the README. This is another example showing how broken the GNU coreutils are: $ echo -e "äää\tüüü\tööö" | gnu-expand -t "5,10,20" äää üüü ööö $ echo -e "äää\tüüü\tööö" | sbase-expand -t "5,10,20" äää üüü ööö This is due to the fact that they are still not UTF8-aware and actually see "ä" as two single characters, expanding the "äää" with 4 spaces to a tab of length 10. The correct way however is to expand the "äää" with 2 spaces to a tab of length 5. One can only imagine how this silently breaks a lot of code around the world. WHAT WERE THEY THINKING?
2015-01-25 08:31:02 -05:00
#* expand yes none
Add mandoc-manpage for expr(1) and mark it as finished in README. Upon further checking, expr(1) turns out to be implicitly UTF-8 compliant.
2015-01-25 10:49:46 -05:00
=* expr yes none
Add column to mark UTF-8 support One major milestone is to have the sbase-tools supporting UTF-8. Tools like cut(1) with the -n flag don't make sense otherwise. And while the gnu coreutils cut(1) blatantly ignores such an important aspect, we will not tolerate this madness and mark it as a TODO in the main README. Since most tools inherently support UTF-8 anyway, this just concerns tools which mangle with text or search in it in special ways.
2015-01-18 13:36:13 -05:00
=* false yes none
Mark fold(1) and grep(1) as finished in the README
2015-01-25 15:33:28 -05:00
#* fold yes none
=* grep yes none
Add mandoc-manpage for head(1) and clean up code and mark it as finished in the README.
2015-01-25 16:01:26 -05:00
=* head yes none
Add column to mark UTF-8 support One major milestone is to have the sbase-tools supporting UTF-8. Tools like cut(1) with the -n flag don't make sense otherwise. And while the gnu coreutils cut(1) blatantly ignores such an important aspect, we will not tolerate this madness and mark it as a TODO in the main README. Since most tools inherently support UTF-8 anyway, this just concerns tools which mangle with text or search in it in special ways.
2015-01-18 13:36:13 -05:00
= hostname non-posix none
=* kill yes none
Add mandoc-manpage for link(1) and mark it as finished in the README.
2015-01-25 16:44:47 -05:00
=* link yes none
Add column to mark UTF-8 support One major milestone is to have the sbase-tools supporting UTF-8. Tools like cut(1) with the -n flag don't make sense otherwise. And while the gnu coreutils cut(1) blatantly ignores such an important aspect, we will not tolerate this madness and mark it as a TODO in the main README. Since most tools inherently support UTF-8 anyway, this just concerns tools which mangle with text or search in it in special ways.
2015-01-18 13:36:13 -05:00
= ln yes none
=* logger yes none
= logname yes none
ls: Implement -c and update manpage Update usage + README as well. Apparently some of the options ( -H and -L) had already been implemented but not reflected in the program usage line.
2015-01-20 11:50:37 -05:00
= ls no -C, -R, -q, -u
Add column to mark UTF-8 support One major milestone is to have the sbase-tools supporting UTF-8. Tools like cut(1) with the -n flag don't make sense otherwise. And while the gnu coreutils cut(1) blatantly ignores such an important aspect, we will not tolerate this madness and mark it as a TODO in the main README. Since most tools inherently support UTF-8 anyway, this just concerns tools which mangle with text or search in it in special ways.
2015-01-18 13:36:13 -05:00
md5sum non-posix none
= mkdir yes none
= mkfifo yes none
= mktemp non-posix none
Mark insane POSIX flags which we are not planning to include into sbase. What's left to discuss is how we're going to handle them in the tools (dump usage() or silently ignore them).
2015-01-23 17:31:46 -05:00
= mv yes (-i)
Add column to mark UTF-8 support One major milestone is to have the sbase-tools supporting UTF-8. Tools like cut(1) with the -n flag don't make sense otherwise. And while the gnu coreutils cut(1) blatantly ignores such an important aspect, we will not tolerate this madness and mark it as a TODO in the main README. Since most tools inherently support UTF-8 anyway, this just concerns tools which mangle with text or search in it in special ways.
2015-01-18 13:36:13 -05:00
= nice yes none
= nl no -d, -f, -h, -l, -n, -p, -v, -w
= nohup yes none
paste yes none
= printenv non-posix none
printf stolen stolen
=* pwd yes none
= readlink non-posix none
= renice yes none
Mark insane POSIX flags which we are not planning to include into sbase. What's left to discuss is how we're going to handle them in the tools (dump usage() or silently ignore them).
2015-01-23 17:31:46 -05:00
= rm yes (-i)
Add column to mark UTF-8 support One major milestone is to have the sbase-tools supporting UTF-8. Tools like cut(1) with the -n flag don't make sense otherwise. And while the gnu coreutils cut(1) blatantly ignores such an important aspect, we will not tolerate this madness and mark it as a TODO in the main README. Since most tools inherently support UTF-8 anyway, this just concerns tools which mangle with text or search in it in special ways.
2015-01-18 13:36:13 -05:00
= rmdir no -p
= sleep yes none
= setsid non-posix none
sort no -m, -o, -d, -f, -i
split yes none
= sponge non-posix none
strings no -a, -n, -t
= sync non-posix none
= tail no -c, -f
= tar non-posix none
Mark tee(1) as finished in the README
2015-01-23 16:04:19 -05:00
=* tee yes none
Add column to mark UTF-8 support One major milestone is to have the sbase-tools supporting UTF-8. Tools like cut(1) with the -n flag don't make sense otherwise. And while the gnu coreutils cut(1) blatantly ignores such an important aspect, we will not tolerate this madness and mark it as a TODO in the main README. Since most tools inherently support UTF-8 anyway, this just concerns tools which mangle with text or search in it in special ways.
2015-01-18 13:36:13 -05:00
test yes none
Update README for touch
2015-01-20 06:22:09 -05:00
= touch no -r
Add column to mark UTF-8 support One major milestone is to have the sbase-tools supporting UTF-8. Tools like cut(1) with the -n flag don't make sense otherwise. And while the gnu coreutils cut(1) blatantly ignores such an important aspect, we will not tolerate this madness and mark it as a TODO in the main README. Since most tools inherently support UTF-8 anyway, this just concerns tools which mangle with text or search in it in special ways.
2015-01-18 13:36:13 -05:00
#* tr yes none
=* true yes none
= tty yes none
= uudecode no -o
= uuencode no -m
= uname yes none
# unexpand yes none
= uniq no -f, -s
= unlink yes none
seq non-posix none
= sha1sum non-posix none
= sha256sum non-posix none
= sha512sum non-posix none
wc yes none
= xargs no -I, -L, -p, -s, -t, -x
= yes yes none
Add an easier to edit "table" of tools in README We need to go through the tools and update this table to reflect current state.
2014-11-20 18:01:56 -05:00
Minor fix for README
2014-02-12 13:39:13 -05:00
The complement of sbase is ubase[1] which is Linux-specific and
Add initial README
2014-02-12 09:34:09 -05:00
provides all the non-portable tools. Together they are intended to
form a base system similar to busybox but much smaller and suckless.
Building
--------
To build sbase, simply type make. You may have to fiddle with
config.mk depending on your system.
You can also build sbase-box, which generates a single binary
containing all the required tools. You can then symlink the
individual tools to sbase-box.
Ideally you will want to statically link sbase. If you are on Linux
we recommend using musl-libc[2].
Portability
-----------
sbase has been compiled on a variety of different operating systems,
including Linux, *BSD, OSX, Haiku, Solaris, SCO OpenServer and others.
Various combinations of operating systems and architectures have also
been built.
You can build sbase with gcc, clang, tcc, nwcc and pcc.
[1] http://git.suckless.org/ubase/
[2] http://www.musl-libc.org/
Reference in New Issue Copy Permalink