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

134 lines
3.1 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.
Prepare POSIX 2013 audit I can't believe we've come this far! The idea is to look at the 2013 POSIX corrigendum for each tool and deep-test features before making the first 0.1 release. To keep the noise low, I'll do this in batches, not on a per-tool- basis (as many of these are trivial to test). In the meantime, I'll also think of a fitting STANDARDS section for the non-POSIX tools. Now that the audits are pretty much done, I can also have a more relaxed view on standards compliance instead of having to dig through some uncleaned mess. To mark this "new beginning", the README has gotten a liftover. The POSIX 2008-column was more or less useless and as I expect the checks to go along pretty quickly, I "reset" the compliance state of all but the non-POSIX tools and will then go along and check every single one of them in the next few days. Apart from the few missing flags and audits, sbase should then be ready to hit the world with the first release after 4 years of work.
2015-03-23 11:22:00 -04:00
The following tools are implemented:
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
Prepare POSIX 2013 audit I can't believe we've come this far! The idea is to look at the 2013 POSIX corrigendum for each tool and deep-test features before making the first 0.1 release. To keep the noise low, I'll do this in batches, not on a per-tool- basis (as many of these are trivial to test). In the meantime, I'll also think of a fitting STANDARDS section for the non-POSIX tools. Now that the audits are pretty much done, I can also have a more relaxed view on standards compliance instead of having to dig through some uncleaned mess. To mark this "new beginning", the README has gotten a liftover. The POSIX 2008-column was more or less useless and as I expect the checks to go along pretty quickly, I "reset" the compliance state of all but the non-POSIX tools and will then go along and check every single one of them in the next few days. Apart from the few missing flags and audits, sbase should then be ready to hit the world with the first release after 4 years of work.
2015-03-23 11:22:00 -04:00
'#' -> UTF-8 support, '=' -> Implicit UTF-8 support, '*' -> Finished,
'|' -> Audited, 'o' -> POSIX 2013 compliant, 'x' -> Non-POSIX,
'()' -> Petty flag
Note in the README that find(1) and sed(1) are lacking manpages
2015-08-04 06:59:04 -04:00
UTILITY MISSING
------- -------
POSIX 2013 audit Mostly manpage-shuffling according to the changes in the corrigendum, wording changes and more idiomatic expressions. All this is finished up by marking the POSIX 2013 conformant tools with .St -p1003.1-2013 which is not available in older mandoc builds or nroff, but which reflects what we actually did, so who cares? This is a huge step and it's not far until we can release sbase 0.1.
2015-03-27 12:22:48 -04:00
=*|o basename .
=*|o cal .
=*|o cat .
=*|o chgrp .
=*|o chmod .
=*|o chown .
Prepare POSIX 2013 audit I can't believe we've come this far! The idea is to look at the 2013 POSIX corrigendum for each tool and deep-test features before making the first 0.1 release. To keep the noise low, I'll do this in batches, not on a per-tool- basis (as many of these are trivial to test). In the meantime, I'll also think of a fitting STANDARDS section for the non-POSIX tools. Now that the audits are pretty much done, I can also have a more relaxed view on standards compliance instead of having to dig through some uncleaned mess. To mark this "new beginning", the README has gotten a liftover. The POSIX 2008-column was more or less useless and as I expect the checks to go along pretty quickly, I "reset" the compliance state of all but the non-POSIX tools and will then go along and check every single one of them in the next few days. Apart from the few missing flags and audits, sbase should then be ready to hit the world with the first release after 4 years of work.
2015-03-23 11:22:00 -04:00
=*|x chroot .
POSIX 2013 audit Mostly manpage-shuffling according to the changes in the corrigendum, wording changes and more idiomatic expressions. All this is finished up by marking the POSIX 2013 conformant tools with .St -p1003.1-2013 which is not available in older mandoc builds or nroff, but which reflects what we actually did, so who cares? This is a huge step and it's not far until we can release sbase 0.1.
2015-03-27 12:22:48 -04:00
=*|o cksum .
=*|o cmp .
Prepare POSIX 2013 audit I can't believe we've come this far! The idea is to look at the 2013 POSIX corrigendum for each tool and deep-test features before making the first 0.1 release. To keep the noise low, I'll do this in batches, not on a per-tool- basis (as many of these are trivial to test). In the meantime, I'll also think of a fitting STANDARDS section for the non-POSIX tools. Now that the audits are pretty much done, I can also have a more relaxed view on standards compliance instead of having to dig through some uncleaned mess. To mark this "new beginning", the README has gotten a liftover. The POSIX 2008-column was more or less useless and as I expect the checks to go along pretty quickly, I "reset" the compliance state of all but the non-POSIX tools and will then go along and check every single one of them in the next few days. Apart from the few missing flags and audits, sbase should then be ready to hit the world with the first release after 4 years of work.
2015-03-23 11:22:00 -04:00
#*|x cols .
POSIX 2013 audit Mostly manpage-shuffling according to the changes in the corrigendum, wording changes and more idiomatic expressions. All this is finished up by marking the POSIX 2013 conformant tools with .St -p1003.1-2013 which is not available in older mandoc builds or nroff, but which reflects what we actually did, so who cares? This is a huge step and it's not far until we can release sbase 0.1.
2015-03-27 12:22:48 -04:00
=*|o comm .
=*|o cp (-i)
Prepare POSIX 2013 audit I can't believe we've come this far! The idea is to look at the 2013 POSIX corrigendum for each tool and deep-test features before making the first 0.1 release. To keep the noise low, I'll do this in batches, not on a per-tool- basis (as many of these are trivial to test). In the meantime, I'll also think of a fitting STANDARDS section for the non-POSIX tools. Now that the audits are pretty much done, I can also have a more relaxed view on standards compliance instead of having to dig through some uncleaned mess. To mark this "new beginning", the README has gotten a liftover. The POSIX 2008-column was more or less useless and as I expect the checks to go along pretty quickly, I "reset" the compliance state of all but the non-POSIX tools and will then go along and check every single one of them in the next few days. Apart from the few missing flags and audits, sbase should then be ready to hit the world with the first release after 4 years of work.
2015-03-23 11:22:00 -04:00
=*|x cron .
POSIX 2013 audit Mostly manpage-shuffling according to the changes in the corrigendum, wording changes and more idiomatic expressions. All this is finished up by marking the POSIX 2013 conformant tools with .St -p1003.1-2013 which is not available in older mandoc builds or nroff, but which reflects what we actually did, so who cares? This is a huge step and it's not far until we can release sbase 0.1.
2015-03-27 12:22:48 -04:00
#*|o cut .
=*|o date .
=*|o dirname .
=*|o du .
=*|o echo .
Add ed(1) - the standard text editor
2015-12-14 07:09:34 -05:00
o ed .
POSIX 2013 audit Mostly manpage-shuffling according to the changes in the corrigendum, wording changes and more idiomatic expressions. All this is finished up by marking the POSIX 2013 conformant tools with .St -p1003.1-2013 which is not available in older mandoc builds or nroff, but which reflects what we actually did, so who cares? This is a huge step and it's not far until we can release sbase 0.1.
2015-03-27 12:22:48 -04:00
=*|o env .
#*|o expand .
#*|o expr .
=*|o false .
Mark manpages as done in the README for find(1) and sed(1)
2015-08-04 14:42:55 -04:00
= find .
Add flock entry in README
2015-10-07 05:24:46 -04:00
=* x flock .
POSIX 2013 audit Mostly manpage-shuffling according to the changes in the corrigendum, wording changes and more idiomatic expressions. All this is finished up by marking the POSIX 2013 conformant tools with .St -p1003.1-2013 which is not available in older mandoc builds or nroff, but which reflects what we actually did, so who cares? This is a huge step and it's not far until we can release sbase 0.1.
2015-03-27 12:22:48 -04:00
#*|o fold .
Mark getconf as audited in README
2015-10-25 19:45:20 -04:00
=*|o getconf (-v)
Mark grep and tftp as audited Gone through the code quite a few times. Been using them frequently without problems.
2015-11-06 05:30:20 -05:00
=*|o grep .
POSIX 2013 audit Mostly manpage-shuffling according to the changes in the corrigendum, wording changes and more idiomatic expressions. All this is finished up by marking the POSIX 2013 conformant tools with .St -p1003.1-2013 which is not available in older mandoc builds or nroff, but which reflects what we actually did, so who cares? This is a huge step and it's not far until we can release sbase 0.1.
2015-03-27 12:22:48 -04:00
=*|o head .
Prepare POSIX 2013 audit I can't believe we've come this far! The idea is to look at the 2013 POSIX corrigendum for each tool and deep-test features before making the first 0.1 release. To keep the noise low, I'll do this in batches, not on a per-tool- basis (as many of these are trivial to test). In the meantime, I'll also think of a fitting STANDARDS section for the non-POSIX tools. Now that the audits are pretty much done, I can also have a more relaxed view on standards compliance instead of having to dig through some uncleaned mess. To mark this "new beginning", the README has gotten a liftover. The POSIX 2008-column was more or less useless and as I expect the checks to go along pretty quickly, I "reset" the compliance state of all but the non-POSIX tools and will then go along and check every single one of them in the next few days. Apart from the few missing flags and audits, sbase should then be ready to hit the world with the first release after 4 years of work.
2015-03-23 11:22:00 -04:00
=*|x hostname .
Add join(1)
2015-04-20 06:23:20 -04:00
=* o join .
POSIX 2013 audit Mostly manpage-shuffling according to the changes in the corrigendum, wording changes and more idiomatic expressions. All this is finished up by marking the POSIX 2013 conformant tools with .St -p1003.1-2013 which is not available in older mandoc builds or nroff, but which reflects what we actually did, so who cares? This is a huge step and it's not far until we can release sbase 0.1.
2015-03-27 12:22:48 -04:00
=*|o kill .
=*|o link .
=*|o ln .
=*|o logger .
=*|o logname .
#* o ls (-C, -k, -m, -p, -s, -x)
Prepare POSIX 2013 audit I can't believe we've come this far! The idea is to look at the 2013 POSIX corrigendum for each tool and deep-test features before making the first 0.1 release. To keep the noise low, I'll do this in batches, not on a per-tool- basis (as many of these are trivial to test). In the meantime, I'll also think of a fitting STANDARDS section for the non-POSIX tools. Now that the audits are pretty much done, I can also have a more relaxed view on standards compliance instead of having to dig through some uncleaned mess. To mark this "new beginning", the README has gotten a liftover. The POSIX 2008-column was more or less useless and as I expect the checks to go along pretty quickly, I "reset" the compliance state of all but the non-POSIX tools and will then go along and check every single one of them in the next few days. Apart from the few missing flags and audits, sbase should then be ready to hit the world with the first release after 4 years of work.
2015-03-23 11:22:00 -04:00
=*|x md5sum .
POSIX 2013 audit Mostly manpage-shuffling according to the changes in the corrigendum, wording changes and more idiomatic expressions. All this is finished up by marking the POSIX 2013 conformant tools with .St -p1003.1-2013 which is not available in older mandoc builds or nroff, but which reflects what we actually did, so who cares? This is a huge step and it's not far until we can release sbase 0.1.
2015-03-27 12:22:48 -04:00
=*|o mkdir .
=*|o mkfifo .
Prepare POSIX 2013 audit I can't believe we've come this far! The idea is to look at the 2013 POSIX corrigendum for each tool and deep-test features before making the first 0.1 release. To keep the noise low, I'll do this in batches, not on a per-tool- basis (as many of these are trivial to test). In the meantime, I'll also think of a fitting STANDARDS section for the non-POSIX tools. Now that the audits are pretty much done, I can also have a more relaxed view on standards compliance instead of having to dig through some uncleaned mess. To mark this "new beginning", the README has gotten a liftover. The POSIX 2008-column was more or less useless and as I expect the checks to go along pretty quickly, I "reset" the compliance state of all but the non-POSIX tools and will then go along and check every single one of them in the next few days. Apart from the few missing flags and audits, sbase should then be ready to hit the world with the first release after 4 years of work.
2015-03-23 11:22:00 -04:00
=*|x mktemp .
POSIX 2013 audit Mostly manpage-shuffling according to the changes in the corrigendum, wording changes and more idiomatic expressions. All this is finished up by marking the POSIX 2013 conformant tools with .St -p1003.1-2013 which is not available in older mandoc builds or nroff, but which reflects what we actually did, so who cares? This is a huge step and it's not far until we can release sbase 0.1.
2015-03-27 12:22:48 -04:00
=*|o mv (-i)
=*|o nice .
#*|o nl .
=*|o nohup .
Mark od(1) and getconf(1) as audited They have just been (re)written, nothing to do here...
2015-10-25 19:42:20 -04:00
=*|o od .
Add pathchk(1) New command, including man page. UTF-8 compatible and should be POSIX-compliant. Signed-off-by: Mattias Andrée <maandree@kth.se>
2016-02-03 14:12:26 -05:00
#* o pathchk .
POSIX 2013 audit Mostly manpage-shuffling according to the changes in the corrigendum, wording changes and more idiomatic expressions. All this is finished up by marking the POSIX 2013 conformant tools with .St -p1003.1-2013 which is not available in older mandoc builds or nroff, but which reflects what we actually did, so who cares? This is a huge step and it's not far until we can release sbase 0.1.
2015-03-27 12:22:48 -04:00
#*|o paste .
Prepare POSIX 2013 audit I can't believe we've come this far! The idea is to look at the 2013 POSIX corrigendum for each tool and deep-test features before making the first 0.1 release. To keep the noise low, I'll do this in batches, not on a per-tool- basis (as many of these are trivial to test). In the meantime, I'll also think of a fitting STANDARDS section for the non-POSIX tools. Now that the audits are pretty much done, I can also have a more relaxed view on standards compliance instead of having to dig through some uncleaned mess. To mark this "new beginning", the README has gotten a liftover. The POSIX 2008-column was more or less useless and as I expect the checks to go along pretty quickly, I "reset" the compliance state of all but the non-POSIX tools and will then go along and check every single one of them in the next few days. Apart from the few missing flags and audits, sbase should then be ready to hit the world with the first release after 4 years of work.
2015-03-23 11:22:00 -04:00
=*|x printenv .
POSIX 2013 audit Mostly manpage-shuffling according to the changes in the corrigendum, wording changes and more idiomatic expressions. All this is finished up by marking the POSIX 2013 conformant tools with .St -p1003.1-2013 which is not available in older mandoc builds or nroff, but which reflects what we actually did, so who cares? This is a huge step and it's not far until we can release sbase 0.1.
2015-03-27 12:22:48 -04:00
#*|o printf .
=*|o pwd .
Prepare POSIX 2013 audit I can't believe we've come this far! The idea is to look at the 2013 POSIX corrigendum for each tool and deep-test features before making the first 0.1 release. To keep the noise low, I'll do this in batches, not on a per-tool- basis (as many of these are trivial to test). In the meantime, I'll also think of a fitting STANDARDS section for the non-POSIX tools. Now that the audits are pretty much done, I can also have a more relaxed view on standards compliance instead of having to dig through some uncleaned mess. To mark this "new beginning", the README has gotten a liftover. The POSIX 2008-column was more or less useless and as I expect the checks to go along pretty quickly, I "reset" the compliance state of all but the non-POSIX tools and will then go along and check every single one of them in the next few days. Apart from the few missing flags and audits, sbase should then be ready to hit the world with the first release after 4 years of work.
2015-03-23 11:22:00 -04:00
=*|x readlink .
POSIX 2013 audit Mostly manpage-shuffling according to the changes in the corrigendum, wording changes and more idiomatic expressions. All this is finished up by marking the POSIX 2013 conformant tools with .St -p1003.1-2013 which is not available in older mandoc builds or nroff, but which reflects what we actually did, so who cares? This is a huge step and it's not far until we can release sbase 0.1.
2015-03-27 12:22:48 -04:00
=*|o renice .
=*|o rm (-i)
=*|o rmdir .
Mark manpages as done in the README for find(1) and sed(1)
2015-08-04 14:42:55 -04:00
# sed .
Prepare POSIX 2013 audit I can't believe we've come this far! The idea is to look at the 2013 POSIX corrigendum for each tool and deep-test features before making the first 0.1 release. To keep the noise low, I'll do this in batches, not on a per-tool- basis (as many of these are trivial to test). In the meantime, I'll also think of a fitting STANDARDS section for the non-POSIX tools. Now that the audits are pretty much done, I can also have a more relaxed view on standards compliance instead of having to dig through some uncleaned mess. To mark this "new beginning", the README has gotten a liftover. The POSIX 2008-column was more or less useless and as I expect the checks to go along pretty quickly, I "reset" the compliance state of all but the non-POSIX tools and will then go along and check every single one of them in the next few days. Apart from the few missing flags and audits, sbase should then be ready to hit the world with the first release after 4 years of work.
2015-03-23 11:22:00 -04:00
=*|x seq .
=*|x setsid .
=*|x sha1sum .
=*|x sha256sum .
=*|x sha512sum .
POSIX 2013 audit Mostly manpage-shuffling according to the changes in the corrigendum, wording changes and more idiomatic expressions. All this is finished up by marking the POSIX 2013 conformant tools with .St -p1003.1-2013 which is not available in older mandoc builds or nroff, but which reflects what we actually did, so who cares? This is a huge step and it's not far until we can release sbase 0.1.
2015-03-27 12:22:48 -04:00
=*|o sleep .
Audit sort(1) and mark it as finished 1) Remove the function prototypes. No need for them, as the functions are ordered. 2) Add fieldseplen, so the length of the field-separator is not calculated nearly each time skipcolumn() is called. 3) rename next_col to skip_to_next_col so the purpose is clear, also reorder the conditional accordingly. 4) Put parentheses around certain ternary expressions. 5) BUGFIX: Don't just exit() in check(), but make it return something, so we can cleanly fshut() everything. 6) OFF-POSIX: Posix for no apparent reason does not allow more than one file when the -c or -C flags are given. This can be problematic when you want to check multiple files. With the change 5), rewriting check() to return a value, I went off-posix after discussing this with Dimitris to just allow arbitrary numbers of files. Obviously, this does not break scripts and is convenient for everybody who wants to quickly check a big amount of files. As soon as 1 file is "unsorted", the return value is 1, as expected. For convenience reasons, check()'s warning now includes the filename. 7) BUGFIX: Set ret to 2 instead of 1 when the fshut(fp, *argv) fails. 8) BUGFIX: Don't forget to fshut stderr at the end. This would improperly return 1 in the following case: $ sort -c unsorted_file 2> /dev/full 9) Other style changes, line length, empty line before return.
2015-08-04 06:45:59 -04:00
#*|o sort (-d, -f, -i)
POSIX 2013 audit Mostly manpage-shuffling according to the changes in the corrigendum, wording changes and more idiomatic expressions. All this is finished up by marking the POSIX 2013 conformant tools with .St -p1003.1-2013 which is not available in older mandoc builds or nroff, but which reflects what we actually did, so who cares? This is a huge step and it's not far until we can release sbase 0.1.
2015-03-27 12:22:48 -04:00
=*|o split .
Prepare POSIX 2013 audit I can't believe we've come this far! The idea is to look at the 2013 POSIX corrigendum for each tool and deep-test features before making the first 0.1 release. To keep the noise low, I'll do this in batches, not on a per-tool- basis (as many of these are trivial to test). In the meantime, I'll also think of a fitting STANDARDS section for the non-POSIX tools. Now that the audits are pretty much done, I can also have a more relaxed view on standards compliance instead of having to dig through some uncleaned mess. To mark this "new beginning", the README has gotten a liftover. The POSIX 2008-column was more or less useless and as I expect the checks to go along pretty quickly, I "reset" the compliance state of all but the non-POSIX tools and will then go along and check every single one of them in the next few days. Apart from the few missing flags and audits, sbase should then be ready to hit the world with the first release after 4 years of work.
2015-03-23 11:22:00 -04:00
=*|x sponge .
POSIX 2013 audit Mostly manpage-shuffling according to the changes in the corrigendum, wording changes and more idiomatic expressions. All this is finished up by marking the POSIX 2013 conformant tools with .St -p1003.1-2013 which is not available in older mandoc builds or nroff, but which reflects what we actually did, so who cares? This is a huge step and it's not far until we can release sbase 0.1.
2015-03-27 12:22:48 -04:00
#*|o strings .
Prepare POSIX 2013 audit I can't believe we've come this far! The idea is to look at the 2013 POSIX corrigendum for each tool and deep-test features before making the first 0.1 release. To keep the noise low, I'll do this in batches, not on a per-tool- basis (as many of these are trivial to test). In the meantime, I'll also think of a fitting STANDARDS section for the non-POSIX tools. Now that the audits are pretty much done, I can also have a more relaxed view on standards compliance instead of having to dig through some uncleaned mess. To mark this "new beginning", the README has gotten a liftover. The POSIX 2008-column was more or less useless and as I expect the checks to go along pretty quickly, I "reset" the compliance state of all but the non-POSIX tools and will then go along and check every single one of them in the next few days. Apart from the few missing flags and audits, sbase should then be ready to hit the world with the first release after 4 years of work.
2015-03-23 11:22:00 -04:00
=*|x sync .
POSIX 2013 audit Mostly manpage-shuffling according to the changes in the corrigendum, wording changes and more idiomatic expressions. All this is finished up by marking the POSIX 2013 conformant tools with .St -p1003.1-2013 which is not available in older mandoc builds or nroff, but which reflects what we actually did, so who cares? This is a huge step and it's not far until we can release sbase 0.1.
2015-03-27 12:22:48 -04:00
=*|o tail .
Prepare POSIX 2013 audit I can't believe we've come this far! The idea is to look at the 2013 POSIX corrigendum for each tool and deep-test features before making the first 0.1 release. To keep the noise low, I'll do this in batches, not on a per-tool- basis (as many of these are trivial to test). In the meantime, I'll also think of a fitting STANDARDS section for the non-POSIX tools. Now that the audits are pretty much done, I can also have a more relaxed view on standards compliance instead of having to dig through some uncleaned mess. To mark this "new beginning", the README has gotten a liftover. The POSIX 2008-column was more or less useless and as I expect the checks to go along pretty quickly, I "reset" the compliance state of all but the non-POSIX tools and will then go along and check every single one of them in the next few days. Apart from the few missing flags and audits, sbase should then be ready to hit the world with the first release after 4 years of work.
2015-03-23 11:22:00 -04:00
=*|x tar .
POSIX 2013 audit Mostly manpage-shuffling according to the changes in the corrigendum, wording changes and more idiomatic expressions. All this is finished up by marking the POSIX 2013 conformant tools with .St -p1003.1-2013 which is not available in older mandoc builds or nroff, but which reflects what we actually did, so who cares? This is a huge step and it's not far until we can release sbase 0.1.
2015-03-27 12:22:48 -04:00
=*|o tee .
=*|o test .
Mark grep and tftp as audited Gone through the code quite a few times. Been using them frequently without problems.
2015-11-06 05:30:20 -05:00
=*|x tftp .
POSIX 2013 audit Mostly manpage-shuffling according to the changes in the corrigendum, wording changes and more idiomatic expressions. All this is finished up by marking the POSIX 2013 conformant tools with .St -p1003.1-2013 which is not available in older mandoc builds or nroff, but which reflects what we actually did, so who cares? This is a huge step and it's not far until we can release sbase 0.1.
2015-03-27 12:22:48 -04:00
=*|o time .
=*|o touch .
#*|o tr .
=*|o true .
=*|o tty .
=*|o uname .
#*|o unexpand .
=*|o uniq .
=*|o unlink .
=*|o uudecode .
=*|o uuencode .
#*|o wc .
Refactor and audit which(1) Use the *at functions instead of building paths manually. We do still have path-building in recurse() and other areas, but the long-term goal is to rid most interfaces of that for practical and security reasons. In this case, it's more or less trivial. Also, refactor the manpage to be more consistent with the others. BUGFIX: Return exit status 3 on error.
2015-04-27 14:01:30 -04:00
=*|x which .
Add whoami(1) including manpage and other stuff. This program is a no-brainer. This was inspired by an initial commit by e@bestmx.net. Thanks!
2015-12-14 04:55:25 -05:00
=*|x whoami .
POSIX 2013 audit Mostly manpage-shuffling according to the changes in the corrigendum, wording changes and more idiomatic expressions. All this is finished up by marking the POSIX 2013 conformant tools with .St -p1003.1-2013 which is not available in older mandoc builds or nroff, but which reflects what we actually did, so who cares? This is a huge step and it's not far until we can release sbase 0.1.
2015-03-27 12:22:48 -04:00
=*|o xargs (-p)
Prepare POSIX 2013 audit I can't believe we've come this far! The idea is to look at the 2013 POSIX corrigendum for each tool and deep-test features before making the first 0.1 release. To keep the noise low, I'll do this in batches, not on a per-tool- basis (as many of these are trivial to test). In the meantime, I'll also think of a fitting STANDARDS section for the non-POSIX tools. Now that the audits are pretty much done, I can also have a more relaxed view on standards compliance instead of having to dig through some uncleaned mess. To mark this "new beginning", the README has gotten a liftover. The POSIX 2008-column was more or less useless and as I expect the checks to go along pretty quickly, I "reset" the compliance state of all but the non-POSIX tools and will then go along and check every single one of them in the next few days. Apart from the few missing flags and audits, sbase should then be ready to hit the world with the first release after 4 years of work.
2015-03-23 11:22:00 -04:00
=*|x yes .
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
README: document sbase-box-install rule
2015-02-28 09:40:16 -05:00
individual tools to sbase-box or run: make sbase-box-install
Add initial README
2014-02-12 09:34:09 -05:00
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