Doug, The 2 cleanest methods I can see are: a) Set the permissions at the OS level at checkout time. If they don't have write permission the checkin will fail (after they've made all their changes 8-D ) b) During checkout, back the real source code to another name 'cool.screen.io.sub.BKP' and remove the original while it is checked out. When checked in, the new version becomes the 'cool.screen.io.sub'. If they uncheck with no changes then put the .BKP back in place.
FWIW, -Baker -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of doug chanco Sent: Thursday, May 15, 2008 3:42 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] locking code question we COULD use source safe as Israel pointed if source code is kept in unix directories they can be samba mounted on a PC and then checked into and out of source safe. The main issue I am trying to get resolved is to lock the record at the pick level , in case someone does nto check out a code and then tries to edit it when another developer already has it checked out, since most of our developers use a "pick aware" editor as long as the record was locked at the pick level, they would get a warning message, teh question is whats the best way to lock program "x" at the pick level? 1. I could AE/ED and lock it that way (programtically of course) but then how do I exit gracefully? 2. I could READU the item in a program and keep that program running forever (at least until the developer checks it back in then the program could terminate) 3. If I could somehow manage to modify the lock table to say that this item is locked and once checked in modify the lock table to release the lock (this is my preferred solution but I am not sure if its doable or if I have the skill to modify the locking table without corrupting it) 4. other iseas/suggestions? thanks all dougc Israel, John R. wrote: > Yes and no. Since basic program files are just Unix Dirs and the > source code is just text, you could map these files via Samba so that > Windows could see it cleanly and use it that way. It might take a > little playing, but we did something like that and it worked to some extent. > Might not be the best way, but I thought I would throw it out. > > There are similar Open Source products for Unix, though I have not had > experience with them. > > > John Israel > Sr. Programmer/Analyst > Dayton Superior Corporation > 721 Richard St. > Dayton, OH 45342 > 937-866-0711 x44380 > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Brutzman, > Bill > Sent: Thursday, May 15, 2008 2:30 PM > To: 'u2-users@listserver.u2ug.org' > Subject: RE: [U2] locking code question > > It appears that SourceSafe is a Microsoft product. Thus, I expect > that it would not be the best fit in a Unix shop. > > --B > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Israel, John R. > Sent: Thursday, May 15, 2008 2:01 PM > To: u2-users@listserver.u2ug.org > Subject: RE: [U2] locking code question > > > I worked at a site that actually used SourceSafe to check in/out > programs. This worked fairly well in a lot of ways, but it is a shift > in how source code is stored and accessed. The nicest thing is the > historic versioning and comparing features. > > John Israel > Sr. Programmer/Analyst > Dayton Superior Corporation > ------- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ > ------- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
