--- shiela-install.pod 2002/12/23 12:00:07 1.16
+++ shiela-install.pod 2002/12/23 12:08:35 1.17
@@ -77,19 +77,21 @@
add to C<$CVSROOT/CVSROOT/importinfo> (the hook for checking import
operations): ``C<ALL $CVSROOT/CVSROOT/shiela --hook=importinfo>''. This
-assumes that you are using a CVS version with RSE patches applied. If
-you use a stock CVS version, you have to skip this step and live with
-the fact that `C<cvs import>' commands cannot be access controlled by
-B<OSSP shiela> (because then this hook does not exists at all).
+assumes that you are using a CVS version with RSE patches applied (see
+below). If you use a stock CVS version, you have to skip this step
+and live with the fact that `C<cvs import>' commands cannot be access
+controlled by B<OSSP shiela> (because then this hook does not exists at
+all).
=item B<6.>
add to C<$CVSROOT/CVSROOT/admininfo> (the hook for checking admin
operations): ``C<ALL $CVSROOT/CVSROOT/shiela --hook=admininfo>''. This
-requires that you are using a CVS version with RSE patches applied. If
-you use a stock CVS version, you have to skip this step and life with
-the fact that `C<cvs admin>' commands cannot be access controlled by
-B<OSSP shiela> (because then this hook does not exists at all).
+requires that you are using a CVS version with RSE patches applied (see
+below). If you use a stock CVS version, you have to skip this step
+and life with the fact that `C<cvs admin>' commands cannot be access
+controlled by B<OSSP shiela> (because then this hook does not exists at
+all).
=item B<7.>
@@ -104,13 +106,13 @@
=item B<9.>
add to C<$CVSROOT/CVSROOT/loginfo> (the hook for performing logging):
-``C<ALL $CVSROOT/CVSROOT/shiela --hook=loginfo %{sVvto}>''. This
-requires that you use a CVS version with RSE patches applied. If you use
-a stock CVS version, use ``C<ALL $CVSROOT/CVSROOT/shiela --hook=loginfo
-%{sVv}>'' instead and live with the fact that B<OSSP shiela>'s run-time
-efficiency is slightly decreased and branch recognition might be less
-correct (because B<OSSP shiela> has to determine details the hard way
-which CVS already would know easily).
+``C<ALL $CVSROOT/CVSROOT/shiela --hook=loginfo %{sVvto}>''.
+This requires that you use a CVS version with RSE patches
+applied (see below). If you use a stock CVS version, use ``C<ALL
+$CVSROOT/CVSROOT/shiela --hook=loginfo %{sVv}>'' instead and live with
+the fact that B<OSSP shiela>'s run-time efficiency is slightly decreased
+and branch recognition might be less correct (because B<OSSP shiela> has
+to determine details the hard way which CVS already would know easily).
=item B<10.>
@@ -178,14 +180,14 @@
8. CVSROOT/loginfo (extra logging after commit)
9. CVSROOT/history (logging of the commit step)
-=item On "C<cvs tag>":
+=item On "C<cvs tag>" (CVS with RSE patches only):
1. CVSROOT/config (general configuration)
2. CVSROOT/modules (determine module names)
3. CVSROOT/taginfo (access control and tag evaluation)
4. CVSROOT/history (logging of the tag step)
-=item On "C<cvs admin>":
+=item On "C<cvs admin>" (CVS with RSE patches only):
1. CVSROOT/config (general configuration)
2. CVSROOT/modules (determine module names)
@@ -194,9 +196,21 @@
=back
+=head1 CVS WITH RSE PATCHES APPLIED
+
+The stock CVS vendor version you can find on http://www.cvshome.org/.
+Although B<OSSP shiela> works fine with just this version, it
+unfortunately lacks some important features which make B<OSSP shiela>'s
+processing less strong. For instance, the stock CVS does not allow
+B<OSSP shiela> to apply access control to the "C<cvs tag>" and "C<cvs
+admin>" commands. Hence Ralf S. Engelschall extended CVS with those
+features (and more) and maintains a patch set in the "cvs" package of
+his B<OpenPKG> project (http://www.ossp.org/). You can find the latest
+patch set under http://cvs.openpkg.org/openpkg-src/cvs/cvs.patches.rse
+
=head1 SEE ALSO
-shiela(1).
+cvs(1), shiela(1).
=head1 AUTHOR
|
