Re: Commitinfo examples

[Mark D. Baushke]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

address@hidden writes:

> I'm trying to deal with some users who habitually commit "useless" changes
> to files.  By "useless" I mean whitespace changes at the front and end of
> line, changing the position of curly-braces, etc.  While I would love to
> flog these people I've been told it would be bad for morale.  My managers
> want me to find a way to enforce, through CVS, some basic coding
> standards.

This is possible, but will not make you popular.

> We run CVS 1.11.5 (willing to upgrade) pserver on an old Solaris 5.6 box.
> 
> I looked through the code for commit_prep in the contrib directory and
> understand it, but it looks like it is designed to run in the local
> directory.   This may be a problem since we use pserver (behind a firewall
> on a secure sub-network).

When running in client/server mode, the repository and the data are
local to the server.

> So...  Am I reading the commit_prep script wrong?

No, but you don't yet realize that a copy of the files being committed
are available to you in the current working directory in which
commit_prep is run and that the 'local' server is set in the $CVSROOT
variable with the path to the Repository directory and files impacted
by change in that directory given on the command line.

> Would it work over pserver? 

Yes.

> If so I could use it as a base for what I'm looking for. If not is
> there any way to do what I'm looking for over pserver?

The commit_prep script, if run from the commitinfo trigger is run on the
server on a copy of the files being committed.

As it runs on the server, it will work with either :pserver: or :ext: or
local cvs repositories.

        Enjoy!
        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQE/vOdl3x41pRYZE/gRArA1AJ4uLL3cOzyZ5KbcLv8tMFu7aMTBOwCeJYoS
rhWmcEQJlFBdXMtJIn/QcDA=
=ri4H
-----END PGP SIGNATURE-----