<h1>Migrating STAR code from CVS to Git</h1> <div style="font-size: 95%;"> - Links to previous discussions - [Proposal for CVS to Git Migration](s1.html) - [Update on CVS to Git Migration](s2.html) - Established two Git repositories - https://github.com/star-bnl/star-sw — All STAR libraries for event reconstruction and simulation - https://github.com/star-bnl/star-mcgen — A separate repo for MC event generators - There is no overlap between the two despite being produced from the same CVS repo - RACF accounts used in CVS are mapped to real user's name and their email using the STAR collaborator database - Bare repository sizes of `star-sw` and `star-mcgen` are 160 and 80 MB respectively (as reported by github) - Migration scripts, user tools, and documentation are available in a support repository - https://github.com/star-bnl/star-git-tools </div>

<h1>Getting and Building STAR code from Git</h1> - To build a release with all the libraries one can merge the code from the two repositories into a single local directory and proceed as usual - For example, to get the code corresponding to the `SL20a` tag do <pre><code data-trim class="shell"> $ mkdir release-SL20a && cd release-SL20a $ curl -sL https://github.com/star-bnl/star-sw/archive/SL20a.tar.gz | tar -xz --strip-components 1 $ curl -sL https://github.com/star-bnl/star-mcgen/archive/SL20a.tar.gz | tar -xz --strip-components 1 </code></pre> - Similarly, to get the most recent code for a "DEV" release replace `SL20a` with `master` in the above example - The code can be compiled and used as usual, e.g. by running `cons` and the `bfc.C` macro - The setup was tested with a few short test jobs executed interactively on the farm - If you find problems with this workflow please let me know