# # Config file for cvs2p4 # # $Id: //guest/perforce_software/utils/cvs2p4/test/config#7 $ # p4 command location (If other than "/usr/local/bin/p4") # $P4 = "/usr/local/bin/p4"; # path to the RCS "co" command # $CO = "/usr/bin/co"; # Perforce server we're using. # $P4PORT = "localhost:1678"; # Perforce client name for the conversion client. # I can't imagine why you'd want to change this, but maybe you can! # (The client is created automatically by bin/dochanges) # $P4CLIENT = "cvs2p4"; # Perforce user name to use during the conversion. # This code defaults it to the user name of the user running # the conversion, but you can override that here if you want. # # (@pwent) = getpwuid($<); if ($#pwent < 7) { print STDERR "$Myname: can't get your passwd file entry.\n"; exit 1; } $P4USER = $pwent[0]; # Top of the module in the p4 depot namespace # $P4_DEPOT = "//depot/Test"; # Top of the CVS module repository to convert # # (Typically, you'll use an absolute path, but it can also be relative # to where you execute the conversion commands from.) # $CVS_MODULE = "test"; # Allow symlinks to directories in the top level of the RCS module. # Useful for partial converts of CVS modules, where you only want # certain subtrees, e.g., you have a cvs module "d" with: # # $CVSROOT/d/x # $CVSROOT/d/y # $CVSROOT/d/z # # ...and you only want to import d/x & d/z; you create # # $CVSROOT/D # $CVSROOT/D/x -> $CVSROOT/d/x # $CVSROOT/D/z -> /d/z # # set CVS_MODULE to "D", and set this: # $SYM_SPECIAL = 1; # Files you don't want. # (Any files matching this regular expression will not be imported). # $IGNOREFILES = "^(.cvsignore)\$"; # Name of the "head" codeline (which will become the "main" branch in # Perforce). Use "head" to get the cvs trunk, or another branch tag # name if you want that branch to become the "main" branch in # Perforce... This needs to be "shemp" to work for the test cases, and # "shemp" should actuall be OK as long as you don't have a branch # named "shemp" in CVS - i.e., the trunk will end up as "main/..." in # Perforce. But if that makes you nervous, you can set this to # "trunk". # $TRUNKLINE = "shemp"; # Conventional branch tag name suffix to remove when importing to # Perforce. (This is a netapp specific thing; our branch tags are # named _BRANCH, but we want the "branches" in the Perforce # depot to be "$P4_DEPOT/"). # $BRANCH_FLASH = "_BRANCH"; # How often (if > 0) to checkpoint. # # (I.e., "1000" means every 1000 change groups, as numbered in the # generated "changes" file) # # Note: this uses the NetApp-local tool "p4d_admin", which, if you're # not at NetApp (and you probably are not, otherwise you'd be me, and # would not bother to read this, right?). Anyway, this will only kick # in when you runs this in the "netapp.com" domain... so you can # probably ignore this entriely. # if ($CVS_MODULE eq "test" && $P4_DEPOT eq "//depot/Test") { $CHECKPOINT_INTERVAL = 10; } else { $CHECKPOINT_INTERVAL = 0; } # Whether to go all the way back to the first rev on the trunk. # (Otherwise, we just go back to the oldest ancestor rev of any # converted branch). # $ALLTHEWAYBACK=1; # Whether to treat CVS tags on 1.1.1.1 revisions in CVS as if they # actually name revision "1.1". # # In some archives initialized with "cvs import", and subsequently # tagged, the tags for files which have not been revised since the # import will point at the 1.1.1.1 revision (which is on the "import" # branch). normally (without this) cvs2p4 will model this, i.e., the # tag for such files will appear in the "import" branch. However, some # users may want to consider the file as having been tagged in the # "main" branch. Setting this option will make cvs2p4 treat the tag as # if it had named the 1.1 revision (which is, presumably, always # identical to the 1.1.1.1 revision after a "cvs import". Note that # repositories which have had several vendor drops could have tags # pointing to other revisions 1.1.1.{n>1}, and this will not help in # such situations! # $IMPORTTAGSPOOF=0; # Whether we're doing selected lines only... # # Typically, you might run "genmetadata" once with this set to 0, # which will print a list of all branch tag names encountered in the # repository. Then, you might want to fill in the <