Loading...
Helix SwarmHelix Swarm
Loading...

README

  • //
  • guest/
  • guillaume_barthelemy/
  • specs/
  • README #2
  • View
  • Commits
  • Open Download .zip Download (2 KB) 
  1. Commenting specs: fo_comment_spec.pl, fi_comment_spec.pl
  2.  
  3. Here are a couple of triggers that allow comments to be added to specs.
  4. This will be of particular interest to those that would like to remember
  5. why they have put that strange rule in the protection table six months
  6. ago, or who requested that typemap in the depot !
  7.  
  8. The triggers allow adding comments persistently without having to resort
  9. to invoking the p4 commands from wrapper scripts. They work like this,
  10. taking the example of the protection table:
  11.  
  12. When running "p4 protect", the first of two triggers kicks in: a form-out
  13. trigger on the protect spec reads the temporary form file generated by the
  14. Perforce server, and matches lines to the keys of a hash table that is read
  15. from a file (call it a comments file). If a match is found then the comment
  16. is inserted just above its matching line in the temporary protection table
  17. form file, which is presented to the superuser running the command.
  18.  
  19. The superuser can then edit the protection table, adding, changing or
  20. removing comments and/or rules.
  21.  
  22. Once done, saving the protection table invokes a form-in trigger. This
  23. trigger parses the protection table form that is full of comments, isolates
  24. each comment in a hash keyed by matching spec rule, and saves the hash
  25. to the "comments file".
  26.  
  27. Here's a typical trigger table entry to achieve the above.
  28.  
  29.  record_comments form-in protect "/usr/local/bin/perl /home/perforce/triggers/fi_comment_spec.pl %formfile% /home/perforce/triggers/protect_comments.inc"
  30.  record_comments form-out protect "/usr/local/bin/perl /home/perforce/triggers/fo_comment_spec.pl %formfile% /home/perforce/triggers/protect_comments.inc"
  31.  
  32. --------------------------
  33.  
  34. Setting a default client: fo_customise_client.pl
  35.  
  36. Form-out trigger that kicks in whenever p4 client is invoked. The script
  37. checks whether the client already exists, and if so exits without doing
  38. anything. Using p4 info seems to be the least expensive way to do that.
  39.  
  40. Otherwise, the client form is modified for a site's preferred defaults.
  41.  
  42. Guillaume Barthelemy
# Change User Description Committed
#2 6381 Guillaume Barthelemy Adding a trigger to change a client's defaults 17 years ago
#1 6380 Guillaume Barthelemy Adding triggers to facilitate the commenting of specs. 17 years ago