ikiwiki/doc/rcs/cvs.mdwn

If you really need to, you can use [[!wikipedia desc="CVS" Concurrent Versions System]]
with ikiwiki.

### Usage
7. Install [[!cpan File::chdir]], [[!cpan File::ReadBackwards]],
[cvsps](http://www.cobite.com/cvsps/), and
[cvsweb](http://www.freebsd.org/projects/cvsweb.html) or the like.
7. 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 module `ikiwiki` (vendor tag IKIWIKI, release tag PRE_CVS),
 * configures the post-commit hook in `CVSROOT/loginfo`.

### To do
* Have `ikiwiki-makerepo` set up NetBSD-like `log_accum` and `commit_prep` scripts that coalesce commits into changesets. Reasons:
    7. 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 `cvsps` and `File::ReadBackwards` code.)
    7. 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|plugins/recentchanges]].)
* 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.
add rcs/cvs 2009-09-10 22:31:58 +02:00			`If you really need to, you can use [[!wikipedia desc="CVS" Concurrent Versions System]]`
			`with ikiwiki.`
add working CVS plugin 2009-08-01 00:17:53 +02:00
Life is simpler on a git branch. 2009-08-16 17:58:28 +02:00			`### Usage`
File::chdir is needed now 2009-09-10 06:59:05 +02:00			`7. Install [[!cpan File::chdir]], [[!cpan File::ReadBackwards]],`
			`[cvsps](http://www.cobite.com/cvsps/), and`
also need File::ReadBackwards now 2009-08-30 07:31:15 +02:00			`[cvsweb](http://www.freebsd.org/projects/cvsweb.html) or the like.`
add install and usage directions, to-do list 2009-08-10 04:06:02 +02:00			`7. Adjust CVS-related parameters in your setup file.`
add working CVS plugin 2009-08-01 00:17:53 +02:00
add install and usage directions, to-do list 2009-08-10 04:06:02 +02:00			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:
add working CVS plugin 2009-08-01 00:17:53 +02:00
			`cvs -q`
			`checkout -P`
			`update -dP`
			`diff -u`
			`rdiff -u`

add install and usage directions, to-do list 2009-08-10 04:06:02 +02:00			`### Implementation details`
			`* [[ikiwiki-makerepo]]:`
			`* creates a repository,`
			* imports `$SRCDIR` into top-level module `ikiwiki` (vendor tag IKIWIKI, release tag PRE_CVS),
no more wrapper wrapper 2009-08-22 09:52:45 +02:00			* configures the post-commit hook in `CVSROOT/loginfo`.
add working CVS plugin 2009-08-01 00:17:53 +02:00
add install and usage directions, to-do list 2009-08-10 04:06:02 +02:00			`### To do`
another reason to use NetBSD's commit_prep and log_accum for CVS 2010-06-26 22:14:50 +02:00			* Have `ikiwiki-makerepo` set up NetBSD-like `log_accum` and `commit_prep` scripts that coalesce commits into changesets. Reasons:
			7. 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 `cvsps` and `File::ReadBackwards` code.)
			`7. 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\|plugins/recentchanges]].)`
add install and usage directions, to-do list 2009-08-10 04:06:02 +02:00			* 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.