disabled l=J 2RP"n 1h 0DlzmJeAqţ m_I|a=J 2RP.emLZ7<git-cvsserver(1) ================ NAME ---- git-cvsserver - A CVS server emulator for Git SYNOPSIS -------- SSH: [verse] export CVS_SERVER="git cvsserver" 'cvs' -d :ext:user@server/path/repo.git co pserver (/etc/inetd.conf): [verse] cvspserver stream tcp nowait nobody /usr/bin/git-cvsserver git-cvsserver pserver Usage: [verse] 'git-cvsserver' [options] [pserver|server] [ ...] OPTIONS ------- All these options obviously only make sense if enforced by the server side. They have been implemented to resemble the linkgit:git-daemon[1] options as closely as possible. --base-path :: Prepend 'path' to requested CVSROOT --strict-paths:: Don't allow recursing into subdirectories --export-all:: Don't check for `gitcvs.enabled` in config. You also have to specify a list of allowed directories (see below) if you want to use this option. -V:: --version:: Print version information and exit -h:: -H:: --help:: Print usage information and exit :: You can specify a list of allowed directories. If no directories are given, all are allowed. This is an additional restriction, gitcvs access still needs to be enabled by the `gitcvs.enabled` config option unless '--export-all' was given, too. DESCRIPTION ----------- This application is a CVS emulation layer for Git. It is highly functional. However, not all methods are implemented, and for those methods that are implemented, not all switches are implemented. Testing has been done using both the CLI CVS client, and the Eclipse CVS plugin. Most functionality works fine with both of these clients. LIMITATIONS ----------- CVS clients cannot tag, branch or perform Git merges. 'git-cvsserver' maps Git branches to CVS modules. This is very different from what most CVS users would expect since in CVS modules usually represent one or more directories. INSTALLATION ------------ 1. If you are going to offer CVS access via pserver, add a line in /etc/inetd.conf like + -- ------ cvspserver stream tcp nowait nobody git-cvsserver pserver ------ Note: Some inetd servers let you specify the name of the executable independently of the value of argv[0] (i.e. the name the program assumes it was executed with). In this case the correct line in /etc/inetd.conf looks like ------ cvspserver stream tcp nowait nobody /usr/bin/git-cvsserver git-cvsserver pserver ------ Only anonymous access is provided by pserve by default. To commit you will have to create pserver accounts, simply add a gitcvs.authdb setting in the config file of the repositories you want the cvsserver to allow writes to, for example: ------ [gitcvs] authdb = /etc/cvsserver/passwd ------ The format of these files is username followed by the crypted password, for example: ------ myuser:$1Oyx5r9mdGZ2 myuser:$1$BA)@$vbnMJMDym7tA32AamXrm./ ------ You can use the 'htpasswd' facility that comes with Apache to make these files, but Apache's MD5 crypt method differs from the one used by most C library's crypt() function, so don't use the -m option. Alternatively you can produce the password with perl's crypt() operator: ----- perl -e 'my ($user, $pass) = @ARGV; printf "%s:%s\n", $user, crypt($user, $pass)' $USER password ----- Then provide your password via the pserver method, for example: ------ cvs -d:pserver:someuser:somepassword server/path/repo.git co ------ No special setup is needed for SSH access, other than having Git tools in the PATH. If you have clients that do not accept the CVS_SERVER environment variable, you can rename 'git-cvsserver' to `cvs`. Note: Newer CVS versions (>= 1.12.11) also support specifying CVS_SERVER directly in CVSROOT like ------ cvs -d ":ext;CVS_SERVER=git cvsserver:user@server/path/repo.git" co ------ This has the advantage that it will be saved in your 'CVS/Root' files and you don't need to worry about always setting the correct environment variable. SSH users r