ftp.nice.ch/pub/next/developer/resources/classes/MOKit.1.0.0.s.tar.gz#/MOKit_1.0.0/README_CVS.rtf

This is README_CVS.rtf in view mode; [Download] [Up]

MOKit docs,  Copyright ©1992, 1993, 1994 by Mike Ferris.  All Rights Reserved.
By Mike Ferris  --  November 21st, 1993

CVS Use


MOKit is now fully capable of existing under cvs control.  This file contains some policies to adhere to concerning cvs use with MOKit.  It is more of a note to myself than to others.

Adding new directories:

	When adding new directories you must be sure to use cvs add to inform cvs of the new stuff.  You must run cvs add recursively for all the added files and directories.  After commiting the new stuff for the first time, make sure to run cvs admin -ko on all added binary files.  This includes the contents of nib wrappers, tiffs, eps, sounds, PB files, rtf files, etc...

Removing obsolete files and directories:

	Use cvs remove to remove old files from the project.  Directories cannot be removed from a repository (at least through cvs commands).  If an entire directory becomes obsolete, remove all its contents.  When checking out a project, the -P option to cvs checkout will prune any checked out directories that end up with no files in them.
	
Checking out the project:
	
	Always run make cvspack in the project directory after checking out, updating or committing MOKit.

Commiting or updating in the project:
	
	Always run make cvsunpack in the project directory before updating or commiting anything.  Then run make cvspack again afterwards.
	
Trimming MOKit products:

	Running make cvstrim in the project directory will remove cvs administrative directories from all compiled products of MOKit.  This is automatically done by the install target.

Versioning and tagging:

	Committing should be done on a semi-regular basis.  Every day or so when the kit is in flux.  Tagging should be done at every release at least.  Any milestone-ish version should be tagged.  When new tags are created make a note in the VersionTags.rtf file (not distributed since it is useless to all but me.)
	

These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Netfuture.ch.