aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDerek Stevens <nilix@nilfm.cc>2021-05-12 20:53:14 -0600
committerDerek Stevens <nilix@nilfm.cc>2021-05-12 20:53:14 -0600
commiteb4238f6f1cd09b508ddf501e44b437aaf9565f0 (patch)
treed511217cbbc96bc1073626b6f6342f3514d24857
parent80d5a8db52eed2f354a9053c25be333ca13c8fef (diff)
update README
-rwxr-xr-xREADME.md12
1 files changed, 3 insertions, 9 deletions
diff --git a/README.md b/README.md
index c7fa617..d5a061b 100755
--- a/README.md
+++ b/README.md
@@ -52,17 +52,11 @@ window centered (its exact geometry is configurable via `config.h`).
### Dependencies, Building, Installation
Being forked from Rio, Ryudo requires `plan9port`, `Xlib`, and `Xt`.
If you enable notifications, it of course requires `notify-send`.
-Make it with `mk ryudo` and then copy the resulting executable `ryudo` to
-somewhere in your **PATH**
-If you try to install it with `mk install` it will probably install
-to `$PLAN9/bin/` under the name `rio`. This is less than ideal but I'm
-not a master of mk, so my protocol is to use a mk target `ryudo` which
-builds the program as `o.rio`, then calls `ryudomagic.sh` to rename
-the program. A proper mkfile is planned before version 1.0.
+Build with `build.sh` (calls `mk` and does some other magic), and install with `install.sh` (will install to a local folder if run as a normal user, or to your `$PLAN9/bin/` if run as root).
-If you have trouble building, you might need to edit the **mkfile** at line 2
-to point to the proper location of your plan9port's **mkwsysrules.sh**.
+If you have trouble building, you might need to edit the `mkfile` at line 2
+to point to the proper location of your plan9port's `mkwsysrules.sh`.
### Bugs and Caveats
Of the bugs and caveats not already mentioned in Rio's readme: