[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Maintaining code in both SVN and CVS

From: Jeremy Aston <jeremy.aston_at_futuremedia.co.uk>
Date: 2004-08-04 05:01:34 CEST

I know this might sound really mad but has anyone tried using
subclipse/svn and cvs together on the same project? Basically I work
as a freelance developer and all my code is held in my own svn
repositiory. I am writing some code for a customer who has a CVS
repository and is not prepared to migrate (grrrr). I am trying to work
out the best strategy for managing my code and I have got two basic
approaches. One is to only CVS "distribution builds". This means I
use SVN to handle incremental version updates but when I have a version
of the source that I want to blat out to the customer then they get a
distribution which is then put in CVS.

The only problem with this is that if the source code is changed on the
cvs version (as it full well may be) then there is going to be problems
keeping source files in sync. This leads me to wonder if it is
possible to have svn and cvs share the same working area. If you set
svn up to ignore cvs control files and vice versa for cvs then I am
guessing it would be possible to use a single working area. Has anyone
tried this? I know this is a general svn question but this list seems
to habour the most hardcore users ;-)

There is a third solution but that is just to use CVS but that is not
really an option since I need to maintain my source code outside (both
technically and commercially) of the customer and they do not have
public access to their cvs server.

advanced cheese for your thoughts.

jez
Received on Wed Aug 4 13:01:34 2004

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.