blob: a8f2f2754590a01ac19bebb716c81aa6b9fa0118 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
|
[[!template id=gitbranch branch=schmonz/cvs author="[[schmonz]]"]]
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/)
(note: probably not [cvsps3](http://www.catb.org/~esr/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
* Expand test coverage and fix bugs.
* 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.
* Do a writeup for [[rcs/details]].
|