Hi,I have been using Subversion to track revisions from icfb. For the most part it works fairly well, however using the various file manipulation capabilities of the Library Manager such as copy and rename results in a big mess. Rather than ignoring the .svn folders, it copies them to a different place. Then when I try to commit the new design with the copied library, Subversion gives errors relating to the improper copy. I hope it's clear what the issue is. Has anyone encountered this problem before? Is there some SKILL code that could be used to call the subversion copy command instead of the usual shell command?
Hi there,From the problem description I gather, that you are talking about the Cadence libraries, rather then the versions of icfb itself.I was always wondering, if somebody is using svn and Cadence libraries together.How did you integrate SVN into the Cadence environment? How do you make Cadence recognize SVN as a DM system?Cheers,Britta
Yes I am using svn to manage the Cadence libraries. At least I am trying to.
How did you integrate SVN into the Cadence environment? How do you make Cadence recognize SVN as a DM system?
Fully integrating a DM system with Cadence (actually with the Cadence GDM system) is a great deal of work. Companies such as our own (ENOVIA MatrixOne, previously Synchronicity) and others that have done this have spent many years getting this to work perfectly. It involves writing a library of functions that is linked into the Cadence system, plus various other scripts. Even then, your problem with the .svn folders would not necessarily be resolved: for a similar issue with our own ".SYNC" folders we persuaded Cadence to specifically exclude them from their copies (I thought they had excluded all ".*" folders, but maybe not.)I'm not personally aware that anyone has written a full integration of Subversion into the GDM system, though it is possible.
I have been digging around the Library folders and noticed that the cdsinfo.tag file plays an important role in whether or not Cadence recognizes a specific folder as a Library folder. The simple summary is that if a cdsinfo.tag file exists with the line CDSLIBRARY, Cadence will take notice of it as a Library. This worked fine with my ".test" folder ( which by the way was copied by Cadence once I included the cdsinfo.tag). The strange bit is that the .svn folder does not have a cdsinfo.tag file, it has cdsinfo.tag.svn-base in .svn/text-base/. Suggestions?Thanks,Brian
The cdsinfo.tag identifies the library directory itself as a library - the file should and must only be present at the library level, not at any level below it. (Strictly, the file is not actually required, since the cds.lib really identifies where the libraries are to the DFII system!)I don't know svn, but I presume the file in the .svn folder is the vault for the main cdsinfo.tag, or some other form of metadata managed by svn.The rules of the Cadence 5X Library structure are, basically:- Any object in a library with no "." in the name is assumed to be a folder and assumed to be a cell of the library.- Any object in a library with a "." in the name is assumed to be a file.This can, of course, cause some issues if you are not careful!The other thing the cdsinfo.tag file contains is a line that tells the system which DM system is managing that library. For example, for a library managed by the DesignSync system, the file would contain:DMTYPE syncBut this is only of use if your DM system fully supports the GDM system.