Stats

  • Locked Locked
  • Replies 9
  • Subscribers 126
  • Views 20732
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Using Subversion for Revision Control with Cadence

archive

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?


Originally posted in cdnusers.org by brose@scanimetrics.com
Parents

  • 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 sync
    But this is only of use if your DM system fully supports the GDM system.


    Originally posted in cdnusers.org by ian.dobinson@matrixone.com
Reply

  • 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 sync
    But this is only of use if your DM system fully supports the GDM system.


    Originally posted in cdnusers.org by ian.dobinson@matrixone.com
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.