Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
As I've been discussing, I'm migrating an existing CVS instance over to CVSNT, on Solaris, both will be on the same box, so I'm wondering if there are any unseen gotchas I may hit. My plan is to install CVSNT on the box first, this way Devs using the old CVSROOT shouldn't see any changes; their old clients pointing to CVSROOT will still be valid. After that I want to create a new repository and start moving groups over one by one. The issue I can now see is that I don't think I can symlink the old CVSROOT to the new one to keep backward compat. Is this correct? I'm all for just having Dev's change their CVSROOT once we've moved them, but Project MGR wants to know if they can keep it, and I can just symlink. My test on my sandbox failed; couldn't even login. Any other 'gotchas' that can be forseen in this situation? I'm assuming just 'mv -f' the files from the old CVSROOT to the new will work, and then I can apply perms from there. Thanks P -- Phil Cryer Application Engineer Express-Scripts ******* Confidentiality Notice ******* This email, its electronic document attachments, and the contents of its website linkages may contain confidential health information. This information is intended solely for use by the individual or entity to whom it is addressed. If you have received this information in error, please notify the sender immediately and arrange for the prompt destruction of the material and any accompanying attachments.