• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. Using Subversion for Revision Control with Cadence

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
archive over 17 years ago

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
  • Cancel
Parents
  • archive
    archive over 17 years ago

    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


    Originally posted in cdnusers.org by brose@scanimetrics.com
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 17 years ago

    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


    Originally posted in cdnusers.org by brose@scanimetrics.com
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information