Subversion locked6/14/2023 ![]() cdsvn Unfortunately, when I do this, I can’t get the scripts to load properly and I no longer have the menu hooks. However, I would like to have the scripts all live in a sub-dir like this icfb_work_dir/cdsvn/ I would run icfb within icfb_work_dir, but the SKILL scripts would reside in the sub-dir. I could also copy the entire contents of CDSVN and paste it into my current icfb working directory and then edit the. I then can go into CDSVN and use THAT directory as my working directory. I had two questions related to your scripts.ġ) I see that if I extract the tar file, I get a CDSVN directory. This is a great resource as I’ve just started to learn the headaches of using Cadence projects with subversion. The tar file contains a svn.cdsinit file which needs to be loaded in your. Untar the cdsvn2.tar file in your Cadence start directory (wherever you type icfb, icms, etc.). You can use the unlockify command (from a UNIX shell) to remove these properties. The addCell and addCellView procedure also puts the correct subversion properties on files to require locking. So, I wrote procedures ( svnAddCell.il, svnAddCellView.il) and associated menus to to perform these tasks. In addition, there are certain things you don’t want added (.cdslck files). I found it tedious to go to the command line and do an svn add for new items all the time. One final note is that subversion won’t place files/directories under version control unless you ask it to ( svn add). The locking mechanism gives users a default way to avoid stepping on each others toes without paralyzing them.Įventually, I found myself locking from the command-line so often, that I created Cadence procedures to do it ( svnLockCell.il and svnLockCellView.il) and associated schematic/layout/symbol menu picks (in the menus directory). This is useful since you may want to try an edit that you don’t intend to check back in while someone else has it locked. Note that locks can be bypassed by chmod‘ing a directory. I also wrote a script (lockify) to recursively put permissions (svn:lock-required) on all files in a directory so that subversion “requires” them to be locked before editing. So, I wrote a python script to recurse down directories and lock all files. The only difficulty with this system is that it works on files only. By giving an svn lock command, subversion will mark the file locked in the repository (thus allowing no one else to lock it) and make it writable in your working copy. By setting the correct properties, files will be dumped out with read-only UNIX permissions. This is where subversion (and not many other version control systems) shines: it has a very unobtrusive locking mechanism. So, it was clear that we needed a locking mechanism. We’d each get stuck when we tried to check-in. ![]() My layout contractor would edit (for LVS) the same cell I was working out without me knowing (and vice versa). This worked well until someone else was working on the same design ( as soon as it went to layout). Lockingįor a while, I went without locking. I have automated steps 3,4,5 in a script called fixtilde.
0 Comments
Leave a Reply. |