RE: Exe files corrupted in SVN after import from CVS
From: Bo Berglund <bo.berglund_at_gmail.com>
Date: Sun, 21 Jan 2018 21:09:58 +0100
On Sat, 20 Jan 2018 13:19:26 -0500, Nico Kadel-Garcia <nkadel_at_gmail.com> wrote:
>I suspect you can simplify the whole situation a great deal by moving
I am leaning toward a completely different approach now concerning the PC (Windows) software development repository:
1) I leave the CVS server running but I confgure it as read-only.
2) I export trunk of the projects that need to be worked on from CVS
3) I start over with an empty SVN repository and import the exported
This way svn will be a smaller size and the content should be OK since the projects are not *converted* from CVS but imported as regular normal projects.
We also use CVS (and now SVN) as a store for drawings and printed circuit board projects (PCB).
We are using an engineering repository for these but I found that the converted structure is less than optimal when using SVN because of the tags and branches directories. In CVS we have a subdirectory for drawing sources (DWG) and another for PDF versions (PDF) and also a subdirectory for the boards (PCB). Like this:
These subdirectories were treated as "projects" during conversion, which has led to a problem since there is now only one tags, trunk and brances dir for ALL of the drawings and another set for all PCB:s etc.
So when I looked at the converted repository there is a total mess in the tags directory because we have used tag names like Rev_A, Rev_B etc for almost all PCB:s and now these are merged and contains an assortment of different unrelated projects...
Seems like I have to scrap the conversion also for Engineering and do something else, but what? Separate repositories for drawings, PDF releases and PCB:s maybe?
(PS: Had to send this as regular email since the posting I made through Gmane seems to have disappeared. DS)
This is an archived mail posted to the Subversion Users mailing list.