Helix SwarmHelix Swarm

README

  • //
  • guest/
  • rick_richardson/
  • perforce/
  • utils/
  • c4/
  • README #1
  • View
  • Commits
  • Open Download .zip Download (2 KB) 
  1. 	c4 -- searches for changes (like CVS), import file trees
  2.  
  3.  
  4. Synopsis:
  5. 	Import or re-import whole file trees with correct add/edit/delete
  6. 	operations;  Search for modified/new/removed files and do the correct
  7. 	edit/add/delete operations (inspired by CVS).
  8.  
  9. Description:
  10. 	C4 was originally created to give p4 a CVS feel, by allowing
  11. 	perforce clients to have writable files and have c4 locate
  12. 	changed files in a way similar to CVS.  This has been expanded
  13. 	to correctly find arbitrary changes between the current top of
  14. 	tree and the client so that whole trees can be imported.  This
  15. 	is routinely used to import updates to external source, including
  16. 	updates that can remove/rename whole directories of files.
  17. 	C4 provides a control file that is placed at the top of
  18. 	each client to set environment variables, such as P4PORT and
  19. 	P4CLIENT.  For more information on what c4 does, read the c4
  20. 	manual.
  21.  
  22.  
  23. Neil Russell
  24. (v1.5, August 1999)
  25.  
  26. ======================================================================
  27. Original README:
  28. ----------------
  29.  
  30.  
  31. 	c4 -- CVS like front end to the Perforce SCM system
  32.  
  33. 			    Neil Russell
  34.  
  35.  
  36. C4 provides a CVS like feel to Perforce's SCM system p4.  C4 is not a
  37. substitute for CVS, in that it does not try to mimic CVS's command
  38. set.  Rather, it provides a workspace (client) where every file is
  39. writable, and can be modified on an adhoc basis.  C4 provides commands
  40. that search a client, looking for files that have been added or
  41. changed, and runs p4 commands on them to add, edit, revert, refresh or
  42. update them.  C4 provides a control file that is placed at the top of
  43. each client to set environment variables, such as P4PORT and P4CLIENT.
  44. For more information on what c4 does, read the c4 manual.
  45.  
  46.  
  47. To build from source:
  48.  
  49. *  Unpack the source code.
  50. *  Change to the source directory (the on you unpacked into), and type "make".
  51. *  If all goes well, copy the resulting binary `c4' into a suitable
  52.    directory (eg. /usr/local/bin).
  53.  
  54. If you discover problems, mail me (caret@c-side.com).
  55.  
  56.  
  57. Neil Russell (December 2, 1997).
# Change User Description Committed
#1 645 Rick Richardson Create banch for adding p4wrapper. 24 years ago