OSSP CVS Repository

ossp - Difference in ossp-pkg/shiela/shiela.pod versions 1.6 and 1.7
Not logged in
[Honeypot]  [Browse]  [Home]  [Login]  [Reports
[Search]  [Ticket]  [Timeline
  [History

ossp-pkg/shiela/shiela.pod 1.6 -> 1.7

--- shiela.pod   2002/12/21 09:20:28     1.6
+++ shiela.pod   2002/12/21 09:42:57     1.7
@@ -1,10 +1,11 @@
 ##
-##  Shiela - CVS Access Control and Logging Facility
+##  OSSP shiela - CVS Access Control and Logging Facility
 ##  Copyright (c) 2000-2002 Ralf S. Engelschall <rse@engelschall.com>
+##  Copyright (c) 2000-2002 The OSSP Project <http://www.ossp.org/>
 ##
-##  This file is part of Shiela, an access control and logging
-##  facility for Concurrent Versions System (CVS) repositories 
-##  which can be found at http://www.ossp.org/pkg/shiela/.
+##  This file is part of OSSP shiela, an access control and logging
+##  facility for Concurrent Versions System (CVS) repositories
+##  which can be found at http://www.ossp.org/pkg/tool/shiela/.
 ##
 ##  This program is free software; you can redistribute it and/or
 ##  modify it under the terms of the GNU General Public  License 
@@ -21,41 +22,41 @@
 ##  Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
 ##  USA, or contact Ralf S. Engelschall <rse@engelschall.com>.
 ##
-##  shiela.pod: Shiela manual page (syntax: POD)
+##  shiela.pod: manual page (syntax: POD)
 ##
 
 =pod 
 
 =head1 NAME
 
-B<Shiela> - Access Control and Logging Facility for CVS
+B<OSSP shiela> - Access Control and Logging Facility for CVS
 
 =head1 VERSION
 
-B<OSSP Shiela> 0.9.3 (21-Dec-2002)
+B<OSSP shiela> 0.9.3 (21-Dec-2002)
 
 =head1 DESCRIPTION
 
-B<Shiela> is an access control and logging facility for use with the
-I<Concurrent Versions System> (CVS). It is intended to be hooked
+B<OSSP shiela> is an access control and logging facility for use with
+the I<Concurrent Versions System> (CVS). It is intended to be hooked
 into CVS's processing through the C<$CVSROOT/CVSROOT/>I<xxx>C<info>
-callbacks. This way B<Shiela> provides access control on a path
-and branch basis to particular repository users and user groups.
+callbacks. This way B<OSSP shiela> provides access control on a path and
+branch basis to particular repository users and user groups.
 
 Additionally, repository operations are monitored, accumulated and
 logged. The lookout of logging messages can be configured individually
 on a module path and branch basis and messages can be both saved to
-files and/or delivered by Email.
+files and/or delivered by email.
 
 =head1 CONFIGURATION
 
-The whole configuration of B<Shiela> takes place in a single
+The whole configuration of B<OSSP shiela> takes place in a single
 configuration file. Per default this is C<$CVSROOT/CVSROOT/shiela.cfg>
 where C<$CVSROOT> is either the environment variable C<CVSROOT> from the
 users environment or the one implicitly provided by CVS because of the
 scope of C<CVS/Root> files or because of an active B<-d> CVS command
 line option. But one can also override the location of the configuration
-file with the B<Shiela> command line option B<--config>.
+file with the B<OSSP shiela> command line option B<--config>.
 
 This file uses a C-style syntax which is described by the following
 grammar rooted at I<config>:
@@ -76,7 +77,7 @@
 So, the syntax has only one recursion and this way is rather simple but still
 powerful enough.
 
-But this is only the general structure as understood by B<Shiela>'s parser.
+But this is only the general structure as understood by B<OSSP shiela>'s parser.
 For semantical reasons only a particular structure is allowed to be created
 with the syntax. This is described in the following.
 
@@ -213,9 +214,9 @@
 
 =item B<History E<lt>pathE<gt>;>
 
-The filesystem path where the B<Shiela> history file is written to.  Do not
-confuse this with the CVS C<history> file. The B<Shiela> history file logs
-only B<Shiela> commits and can be used to reconstruct commit operations later.
+The filesystem path where the B<OSSP shiela> history file is written to.  Do not
+confuse this with the CVS C<history> file. The B<OSSP shiela> history file logs
+only B<OSSP shiela> commits and can be used to reconstruct commit operations later.
 Example: C<History CVSROOT/shiela.log;>
 
 =item B<Module E<lt>modulepathE<gt> E<lt>modulenameE<gt> { ... };>
@@ -351,7 +352,7 @@
 
 =item B<CVS E<lt>pathE<gt>;>
 
-This overrides the path to the CVS executable. Per default B<Shiela>
+This overrides the path to the CVS executable. Per default B<OSSP shiela>
 determines this automatically through the inherited C<$PATH> variable.
 Use this either if you have CVS not in C<$PATH> or if you have multiple
 CVS instances installed.
@@ -359,7 +360,7 @@
 =item B<Sendmail E<lt>pathE<gt>;>
 
 This overrides the path to the Sendmail executable. Per default
-B<Shiela> determines this automatically through the inherited C<$PATH>
+B<OSSP shiela> determines this automatically through the inherited C<$PATH>
 variable. Use this either if you have Sendmail not in C<$PATH> or if you
 have multiple Sendmail instances installed.
 
@@ -464,31 +465,31 @@
 and uses the features of the latest CVS versions (especially those of
 the enhanced CVS variant from OSSP). So in April 2000 he decided to
 rewrite the functionality of C<log_accum.pl>, C<commit_prep.pl> and
-C<cvs_acls.pl> from scratch. The result is B<Shiela>.
+C<cvs_acls.pl> from scratch. The result is B<OSSP shiela>.
 
-The name B<Shiela> was choosen just by coincidence and has no related
-meaning. It was just that while the program was written, a code-name
-was needed. And because Engelschall's first baby was forthcoming and
-Ralf and Daniela Engelschall reviewed lots of names, one of the names
-Ralf liked was B<Shiela>. So the code-name became B<Shiela> and as it is
-often with code-names, they remain forever... ;)
+The name B<OSSP shiela> was choosen just by coincidence and has no
+related meaning. It was just that while the program was written,
+a code-name was needed. And because Engelschall's first baby was
+forthcoming and Ralf and Daniela Engelschall reviewed lots of names, one
+of the names Ralf liked was B<Shiela>. So the code-name became B<OSSP
+shiela> and as it is often with code-names, they remain forever... ;)
 
 =head1 LOCATIONS
 
 =over 4
 
-=item B<http://www.ossp.org/pkg/shiela/>
+=item B<http://www.ossp.org/pkg/tool/shiela/>
 
-Here you can find the official B<Shiela> homepage. 
+Here you can find the official B<OSSP shiela> homepage. 
 
-=item B<ftp://ftp.ossp.org/pkg/shiela/>
+=item B<http://cvs.ossp.org/pkg/tool/shiela/>
 
-Here you can find the latest B<Shiela> release versions as
-distribution tarballs.
+Here you can find the latest B<OSSP shiela> development sources.
 
-=item B<:pserver:anonymous@cvs.ossp.org:/e/ossp/cvs>, module B<shiela>
+=item B<ftp://ftp.ossp.org/pkg/tool/shiela/>
 
-Here you can find the latest B<Shiela> development version.
+Here you can find the latest B<OSSP shiela> release versions as
+distribution tarballs.
 
 =back
 

CVSTrac 2.0.1