If you really need to, you can use CVS with ikiwiki.
Usage
- Install File::chdir, File::ReadBackwards, cvsps, and cvsweb or the like.
- Adjust CVS-related parameters in your setup file.
Consider creating $HOME/.cvsrc
if you don't have one already; the plugin doesn't need it, but you yourself might. Here's a good general-purpose one:
cvs -q
checkout -P
update -dP
diff -u
rdiff -u
Implementation details
- ikiwiki-makerepo:
- creates a repository,
- imports
$SRCDIR
into top-level moduleikiwiki
(vendor tag IKIWIKI, release tag PRE_CVS), - configures the post-commit hook in
CVSROOT/loginfo
.
- CVS multi-directory commits happen separately; the post-commit hook sees only the first directory's changes in time for recentchanges. The next run of
ikiwiki --setup
will correctly re-render such a recentchanges entry. It should be possible to solve this problem with NetBSD'scommit_prep
andlog_accum
scripts (see below).
To do
- Instead of resource-intensively scraping changesets with
cvsps
, haveikiwiki-makerepo
set up NetBSD-likelog_accum
andcommit_prep
scripts that coalesce and keep records of commits.cvsps
can be used as a fallback for repositories without such records. - Perhaps prevent web edits from attempting to create
.../CVS/foo.mdwn
(and.../cvs/foo.mdwn
on case-insensitive filesystems); thanks to the CVS metadata directory, the attempt will fail anyway (and much more confusingly) if we don't.