On Thu, 4 Apr 2002, Saroj Dalal wrote: > Kaz, my problem is little bit different. > > souce code and its makefile is stored under cvs. cvs admin will build source > code everytime for every change. > > There are 5-6 persons working on this source code and makefile. so each user > checkout whole source code and makefile in their home directories, edit > source code and makefile, and then checkin source code into cvs but not > checkin Makefile. each users Makefile is different. each user compile in > their own home directory and then push changed source code into cvs except > makefile. admin of cvs will build the source code..
The source code won't build if it contains references to functions that exist in new source files that the admin's Makefile doesn't know about. This will make the admin upset. > Is their any way that each user can checkout all files, edit all files, > checkin all files except makefile. Why don't you call the central makefile ``Makefile.master'' or something like that. Then the users can have a local file called Makefile which is not known to CVS, and therefore won't trigger any commits. They can still push important changes into Makefile.master. Or teach your users about the -f option of make, by which they can select alternate makefiles, and about the shell alias command by which they can make command line options like ``-f My_Makefile'' sticky. -- Meta-CVS: solid version control tool with directory structure versioning. http://users.footprints.net/~kaz/mcvs.html _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
