On Sep 17, 2005, at 18:18, Dale Hirt wrote:
> Hamilton Chua wrote:
>> I have code from an open source project in a cvs repository.
>> I would like to use subversion version control on a new project
>> based on the
>> source code from the open source project mentioned above.
>> I would like to be able to get updates from the cvs repository of
>> the open
>> source project as much as possible and contriubte code back to
>> this cvs
>> repository, the problem is that I am using subversion.
>> My initial idea was to checkout a cvs working copy from the open
>> project repository and check this in to my subversion repository. Yes
>> everything including the CVS directories.
>> So I checked out a working copy from my personal subversion
>> repository. On
>> this working copy I would occassionally do a cvs update to
>> retrieve updates
>> from the cvs repository of the open source project and then svn
>> Will this work or is this a recipe for disaster ?
> It should work. Create a local repository and run some tests on
> it. See what
> comes up.
If the cvs update causes files in the working copy to be added, an
svn add will not have been performed, and you'll have to run svn
status to determine what files have been added, and manually svn add
them before committing. If the cvs update causes files in the working
copy to be deleted, an svn delete will not have been performed, and
Subversion will complain that files it thought were under its control
are no longer there, and getting out of that situation will likely be
problematic. The only way this could successfully work is if the list
of files in the project never changes, which is probably an
optimistic assumption to make.
I think you'll have better luck taking periodic snapshots from the
code in the CVS repository, either from their stable releases or just
weekly or whatever works for you, and importing these into Subversion
using svn_load_dirs.pl. See the section in The Book on Vendor Branches:
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sun Sep 18 02:58:13 2005