Re: [viewvc-users] Using an Existing ViewVC CVS mySQL db with SVN
"C. Michael Pilato" <[email protected]>
| Newsgroups | gmane.comp.version-control.cvs.viewcvs.user |
|---|---|
| Organization | CollabNet, Inc. |
| Message-ID | <4BA2925D.1050507__3673.48906952447$1268945518$gmane$org@collab.net> |
Ravi K Pattalachinti wrote: > We are in the process of migrating an existing CVS system to SVN. We are > going to use ViewVC as the web client for browsing the new repository. > We also have an existing mySQL commit database. When we do the > conversion to subversion, can I point ViewVC to commit changes to this > already existing database? Or do I have to convert this database to be > compatible with SVN? > > (i.e.) > > Can I bypass the following 2 steps:- > > To build a database of all the commits in the Subversion repository > /home/svn, invoke: "./svndbadmin rebuild /home/svn". > If you want to update the checkin database, invoke: "./svndbadmin update > /home/svn". Hrm... I don't know if it's ever been tried! My gut instinct is that you'll be disappointed with the results of trying, though. The revision number schemes are completely different between the two systems, so even if you managed to get the old CVS data to co-exist with the new Subversion data, any links you click from specific revisions in the query results will lead to bogus ViewVC URLs. It's probably best to regenerate the database using your converted Subversion repository history. -- C. Michael Pilato <[email protected]> CollabNet <> www.collab.net <> Distributed Development On Demand ------------------------------------------------------ http://viewvc.tigris.org/ds/viewMessage.do?dsForumId=4255&dsMessageId=2461839 To unsubscribe from this discussion, e-mail: [[email protected]].
signature.asc
(application/pgp-signature, 197 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkuikl0ACgkQokEGqRcG/W4QuACgzxqBFfxoh1jGwc6GjKuzrP2x 2h4AnjhaW5X5dEfATpu2Y+iXn8uBzoK/ =TFYx -----END PGP SIGNATURE-----