If you have not already done so, the shared files should be part of some independent module. A library with its own build script for example. That way work on the library requires an explicit module checkout.
Concurrent checkouts should not be a problem with or without notification. That's the CVS way of doing thing as you know. Instead of notification you can just assume everybody is editing the same file. That's highly unlikely but if you assume that you will be fine IMO. If that's not warm and fuzzy enough you can still use notifications: http://borglab.media.mit.edu/cvsbook/cvsbook_5.html -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aaron Jackson Sent: Wednesday, June 08, 2005 12:40 PM To: info-cvs@gnu.org Subject: File Checked Out Notification Thanks for all the help on my previous problem, now I have a new one. I'm working on a system where multiple developers are working on many of the same projects and some of the files overlap. Is there some way to notify someone when they check out a file to tell them that another user has checked out that file recently and not checked in the changes or to set a flag that does the same thing. I might have to write an app to do this, but I'm really looking more for something that already exists that will work with a pserver set up to preform these notifications. They can be e-mail notices or Windows and linux broadcast messages. Thanks for any input, Yolan ************************************************* * Yolan (Aaron Jackson) [EMAIL PROTECTED] * * http://mlug.missouri.edu/~yolan/ * * AIM: YolanLINUX, YolanOTHER, YolanLAPTOP * * ICQ: 74624109 * ************************************************* * Doubling Technologies * ************************** _______________________________________________ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs _______________________________________________ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
