If you really need to, you can use CVS with ikiwiki.
- Install File::chdir, File::ReadBackwards, cvsps, and cvsweb or the like.
- Adjust CVS-related parameters in your setup file.
$HOME/.cvsrc if you don't have one already; the
plugin doesn't need it, but you yourself might. Here's a good
cvs -q checkout -P update -dP diff -u rdiff -u
- creates a repository,
$SRCDIRinto top-level module
ikiwiki(vendor tag IKIWIKI, release tag PRE_CVS),
- configures the post-commit hook in
- Expand test coverage and fix bugs.
ikiwiki-makereposet up NetBSD-like
commit_prepscripts that coalesce commits into changesets. Reasons:
- Obviates the need to scrape the repo's complete history to
determine the last N changesets. (Repositories without such
records can fall back on the
- Arranges for ikiwiki to be run once per changeset, rather than CVS's once per committed file (!), which is a waste at best and bug-inducing at worst. (Currently, on multi-directory commits, only the first directory's changes get mentioned in recentchanges.)
- Obviates the need to scrape the repo's complete history to determine the last N changesets. (Repositories without such records can fall back on the
- Perhaps prevent web edits from attempting to create
.../cvs/foo.mdwnon case-insensitive filesystems); thanks to the CVS metadata directory, the attempt will fail anyway (and much more confusingly) if we don't.
- Do a writeup for details.