ikiwiki/doc/rcs/cvs.mdwn

28 lines
1.6 KiB
Plaintext
Raw Normal View History

2009-09-10 22:31:58 +02:00
If you really need to, you can use [[!wikipedia desc="CVS" Concurrent Versions System]]
with ikiwiki.
2009-08-01 00:17:53 +02:00
2009-08-16 17:58:28 +02:00
### Usage
2009-09-10 06:59:05 +02:00
7. Install [[!cpan File::chdir]], [[!cpan File::ReadBackwards]],
[cvsps](http://www.cobite.com/cvsps/), and
2009-08-30 07:31:15 +02:00
[cvsweb](http://www.freebsd.org/projects/cvsweb.html) or the like.
7. Adjust CVS-related parameters in your setup file.
2009-08-01 00:17:53 +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:
2009-08-01 00:17:53 +02:00
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),
2009-08-22 09:52:45 +02:00
* 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|plugins/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's `commit_prep` and `log_accum` scripts (see below).
2009-08-01 00:17:53 +02:00
### To do
* Instead of resource-intensively scraping changesets with `cvsps`, have `ikiwiki-makerepo` set up NetBSD-like `log_accum` and `commit_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.