Make apenwarr/redo installable on windows and work with uv tool install
262d272f29
As named, the file would be extracted by git on macOS, then (un)helpfully normalized by the macOS filesystem. After that, "git clean -fdx" would delete the file, since it no longer had the expected name, so git thought it wasn't part of its repo. I considered pre-normalizing the filename, but a) that would break on any future OS that normalizes differently; and b) that means we won't test denormalized filenames. Instead, we'll remove the directory from git, and create it from sh instead, then figure out what name it got really created as, and then pass the "real" name to redo. |
||
|---|---|---|
| bin | ||
| contrib/bash_completion.d | ||
| docs | ||
| minimal | ||
| redo | ||
| redoconf | ||
| t | ||
| .gitignore | ||
| .pylintrc | ||
| all.do | ||
| clean.do | ||
| do | ||
| install.do | ||
| LICENSE | ||
| Makefile | ||
| MANIFEST.in | ||
| mkdocs.yml | ||
| README.md | ||
| setup.py | ||
| test.do | ||
redo - a recursive build system
Smaller, easier, more powerful, and more reliable than make.
This is an implementation of Daniel J. Bernstein's redo build system. He never released his version, so other people have implemented different variants based on his published specification.
This version, sometimes called apenwarr/redo, is probably the most advanced one, including parallel builds, improved logging, extensive automated tests, and helpful debugging features.
To build and test redo, run:
./do -j10 test
To install it, run something like this:
DESTDIR= PREFIX=/usr/local ./do -j10 install
- View the documentation via readthedocs.org
- Visit the source code on github
- Discussions and support via the
mailing list (archives).
You can subscribe by sending any email message to
redo-list+subscribe@googlegroups.com(note the plus sign). You can send questions or feedback (with or without subscribing) by sending messages toredo-list@googlegroups.com.