Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Value of -cvspath determines package name: it's the last component of the path. Value of -branch defaults to MAIN.  If -branch is specified and is anything other than MAIN, -custom must be used and its value must follow the form for tags along a branch, namely  dd-dd-dd-aadd where all the d's are digits and the a's are alphabetic characters, e.g. 01-02-00-gr01.  If -custom is specified for a  main branch tag its value must be of the form dd-dd-dd.

Examples

Code Block

//simplest example.  Just tag a pkg
stag -notes="Some comments" -patch -cvspath=xmlBase

//tag pkg which happens to be contained in another pkg
stag -notes="Tagging a subpackage" -minor cvspath=celestialSources/GRB   

//tag pkg which contains children (GRB, etc.). Doesn't tag the children
stag -notes="Tagging parent" -minor cvspath=celestialSources  

//tag along a branch
stag -notes="Tagging along a branch" -branch=GlastRelease-15-49-02 custom=05-04-11-gr01 -cvspath=xmlBase

What will happen

In case one of -major, -minor or -patch has been specified, stag will generate the new version string by looking up the "highest" tag along the main branch, incrementing the specified field and zeroing fields to the right, if any, and finally prepending with the package name derived from the value of -cvspath. In the case of a custom string, stag merely prepends the package name.

...