On Friday, October 4, 2002, at 12:32 AM, Frederic Brehm wrote:
> At 08:13 PM 10/2/2002, Ken Williams wrote: >>> Use your build system (make?) to fix the type/creator codes. >> >> I'm not using a build system. I'm just sharing project data. >> >> This file is a database that the people working on this >> project need to access. We each update it often, potentially, >> so we use 'cvs watch on' and 'cvs edit' to manage >> concurrency. In this way CVS is a good tool for sharing it, >> *except* for the fact that the file breaks every time we do >> updates. > > How about making a simple two line script that performs the > update and then fixes the type/creator codes? It shouldn't be > hard to get other people on the project to use the script since > it will make their life easier. > That doesn't really work. This is part of a larger repository. The nature of using CVS is that you don't know in advance when any particular file in the repository has changed - you just type 'cvs update' and get the changes on all files distributed to you. So in order for your idea to work, people would have to use the new script/alias when doing updates from any place in the working directory that could possibly update this file. Anyway, the practical hurdles here have been too great, I think I'm giving up on it. -Ken _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
