refinement

simexec/packaging.md

@@ -8,33 +8,43 @@ I won't sue you.
 
 ## Files
 
-Simexec is a single C file (`simexec.c`) that builds to a single executable,
+- `src/simexec`
-which should be named `simexec` and placed in a user-accessible binaries
+	- Can be moved to a system sources directory if it's desirable to keep
-directory. A `Makefile` is provided as courtesy but isn't really necessary.
+		system sources on hand. Doesn't reference anything else in the
+		repository.
 
-The `src/simexec` directory can be moved to a system sources directory if you
+- `simexec.1`
-wish to keep the source on hand; it doesn't reference anything else in the
+	- Included manual page for `simexec`. Can be placed in the appropriate
-repository.
+		manual pages directory. If it displays weirdly and your fix is
+		portable, mail me and I'll probably bring it upstream.
+ 
+- `simexec.c`
+	- A single C file that builds to a single executable, which should be
+		named `simexec`.
 
-The included manual page, `simexec.1` can be placed in the appropriate manual
+- `simexec`
-pages directory. If it displays weirdly feel free to e-mail me and I'll attempt
+	- Program binary. Should be placed in a user-accessible binaries
-to fix it.
+		directory.
+
+## Dependencies
+
+- `<sysexits.h>`
+	- Ignored if `EX_USAGE` is already defined.
+
+- C standard library
 
 ## Compilation
 
-On systems that provide `<sysexits.h>`, the following is all that's needed:
-
 ```
 cc -o simexec simexec.c
 ```
 
-If you're not sure whether your system provides `<sysexits.h>`, try it and see.
+Or without `<sysexits.h>`:
-If it doesn't work, compile `simexec.c` with the following:
 
 ```
 cc -DEX_USAGE=1 -o simexec simexec.c
 ```
 
-Other than `<sysexits.h>` simexec(1) only relies on headers found in the C
+## Known packages
-standard library. Outside of POSIX environments `simexec.c` probably won't work
+
-but it wouldn't be of much use anyway.
+- [On the Arch User Repository](https://aur.archlinux.org/packages/simexec-git).