» Content »pkg://ClearCase-Wrapper-MGi-0.19.tar.gz:27731
/ info downloads
This directory contains files which can be used to configure the wrapper
for specific needs, either on a site on a user basis.
VobPathConv.pm (and its pod files) does however not require any configuration
and may be used as such. I may even consider to extract it and publish it
as a separate package in its own, albeit modest, right.
It offers functions to convert paths from Windows to Unix, using the registry
to map the tags in associated regions.
It must be installed in the @INC path as ClearCase::VobPathConv.
The remaining files are mostly concerned with locking and unlocking label
types owned by other people (colleagues, members of the same group, vob
The lack of such an ability is considered a bug in ClearCase, and is the
object of an RFE (currently rejected...). It defeats the use of locking in
ForceLockSudo.pm implements the simplest, safest and most efficient solution,
from unix. As its alternatives, dealing with cases in which this superior
solution could not be used, it is meant to be installed in the @INC path,
under a ClearCase directory, and accessed via an environment variable
This is so its use would not penalize functions which do not require locking.
Two other versions are provided for now, one for unix, and one for Windows
These can be used as examples or a templates. They require some customization.
The two latter build upon 'locklbtype', a standalone script, to be installed
suid enabled, owned by an account, which is itself authorized in the ssh
configurations of the respective vob owners of all vobs in the local region,
to run locking commands. It acts as a switch, allowing to simplify the
maintainance of the ~/.ssh/authorized_keys files.
The customization it requires is mostly the name of the host running an sshd
daemon which it will use. One needs to avoid using 'localhost' here, so that
different host keys do not overwrite each other in the ~/.ssh/known_hosts
One may also set the name of the log used to save the identity of the
unlocking users (for lock events, this is saved in a comment of the locks).
The paths to ssh and cleartool are likely to be satisfying.
In order to use this script, you need to define a pair of functions, for
locking and unlocking.
An example of .clearcase_profile.pl sets the ipc mode for all commands apart
for setview (unavailable then, assuming the wrapper itself is used from a vob).
The unix version of the ClearCase::ForceLock module, is meant to invoke
locklbtype via a system call, therefore using the suid bit mechanism offered
by unix shells.
The only customization is the path to the locklbtype utility.
In a Windows environment, the related module fills the same role, but
invokes the suid script on a unix host, via ssh.
It depends on a long list of modules, which I could successfully install
on: cygwin 1.7 / perl 5.10 / libgmp-devel 4.3.1-1, libssh2
and which I don't desperate yet (failing for now on Math::GMP) to install on:
Windows Vista / Active perl 5.10 / GMP-4.1.2
Note that these are just the versions I use, and which work for me.
I cannot claim that this list is a minimal requirement.