1[[!template id=gitbranch branch=schmonz/cvs author="[[schmonz]]"]]
2
3If you really need to, you can use [[!wikipedia desc="CVS" Concurrent
4Versions System]] with ikiwiki.
5
6### Usage
77. Install [[!cpan File::chdir]], [[!cpan File::ReadBackwards]],
8   [cvsps](http://www.cobite.com/cvsps/)
9   (note: probably not [cvsps3](http://www.catb.org/~esr/cvsps/)), and
10   [cvsweb](http://www.freebsd.org/projects/cvsweb.html) or the like.
117. Adjust CVS-related parameters in your setup file.
12
13Consider creating `$HOME/.cvsrc` if you don't have one already; the
14plugin doesn't need it, but you yourself might. Here's a good
15general-purpose one:
16
17    cvs -q
18    checkout -P
19    update -dP
20    diff -u
21    rdiff -u
22
23### Implementation details
24* [[ikiwiki-makerepo]]:
25    * creates a repository,
26    * imports `$SRCDIR` into top-level module `ikiwiki` (vendor tag
27      IKIWIKI, release tag PRE_CVS),
28    * configures the post-commit hook in `CVSROOT/loginfo`.
29
30### To do
31* Expand test coverage and fix bugs.
32* Have `ikiwiki-makerepo` set up NetBSD-like `log_accum` and
33  `commit_prep` scripts that coalesce commits into changesets. Reasons:
34    7. Obviates the need to scrape the repo's complete history to
35       determine the last N changesets. (Repositories without such
36       records can fall back on the `cvsps` and `File::ReadBackwards`
37       code.)
38    7. Arranges for ikiwiki to be run once per changeset, rather
39       than CVS's once per committed file (!), which is a waste at
40       best and bug-inducing at worst. (Currently, on multi-directory
41       commits, only the first directory's changes get mentioned
42       in [[recentchanges|plugins/recentchanges]].)
43* Perhaps prevent web edits from attempting to create `.../CVS/foo.mdwn`
44  (and `.../cvs/foo.mdwn` on case-insensitive filesystems); thanks
45  to the CVS metadata directory, the attempt will fail anyway (and
46  much more confusingly) if we don't.
47* Do a writeup for [[rcs/details]].
48