Introduction

The program msrt provides a simple way for you to install, build and manage the MINOS offline codebase on your system. It does this by boot strapping the build and release system (SRT), as well as simplifying the periodic updating and building of the code. It operates on the so called "base" releases (development or frozen), of which a site typically has one or more central versions.

By default, msrt checks out a copy of the MINOS offline code from the main (CVS) code repository in a read-only fashion (no commit possible). You can still build, run and locally modify the code. If you want to have any changes committed then it is possible, and easy, to switch your code base to a read-write access method (see msrt migrate). You local "test" releases can have access methods independent of the base release (see SRT's cvsmigrate).

After the code is built, you can use msrt to help with routine updating and rebuilding.

Msrt can easily be adapted to other groups SRT systems

Getting `msrt`

There are a couple of ways to get the msrt program:

Via anonymous cvs:

cvs -d :pserver:anonymous@minoscvs.fnal.gov:/cvs/minoscvs/rep1 login
password: anoncvs
cvs -d :pserver:anonymous@minoscvs.fnal.gov:/cvs/minoscvs/rep1 get setup/msrt
(setup/ is created, you can now copy msrt to some place in your PATH)

Via the web: msrt

Using msrt

msrt is "self documenting" in the sense that it carries its documentation around with it. For a brief listing of what it can do simply type:

    msrt

For the full documentation type:

    msrt help

Or, click on the above link.

New users should follow the 12 STEP PROGRAM section of this help output. It will walk you through what is needed to start from zero and end up with a working offline software setup.

Prepare for proxy files

If during the 12 step program you didn't create a site-wide cache for proxy resolution (step 6), do so before issuing "msrt release" or "msrt update" commands. Existing SRT installations can use the instructions for transitioning from old to new approach for handling auxillary files.

SRT_CXX issues

Although not usually necessary, it is possible to specify which GCC version one is using. Issues regarding this are discussed on this page.

Other things you can do

The above showed the basic steps to getting the "development" release installed and built. You can use msrt to do other things as well. Here is list of common things:

Update your (development) release with the latest from the repository?
```
    msrt update
```
Clean all bins/libs from the release:
```
    msrt clean
```

Or just a subset:

    msrt clean PackageOne PackageTwo PackageThree

Update just a subset:

    msrt update PackageOne PackageTwo PackageThree

Build a subset:

    msrt build PackageOne PackageTwo PackageThree

Add a package (which is already in CVS)
```
    msrt update NewPackage
```
This will also add an entry into your local "packages" file for that release. Be aware of this if you ever commit the packages file. The entries will be appended, so check the bottom of the file.
Update the local database
```
    msrt filldb -U <URL> -u <user> -p <password>
```
The URL will look something like:
```
    mysql://localhost/offline
```
where "localhost" might be your full host name.
Most things (release, update, build, clean) that are done on the default "development" release can be done on one of the "frozen" releases by simply specifying the release:
```
    msrt release -r RX.Y.Z
    msrt build -r RX.Y.Z
    msrt update -r RX.Y.Z
    msrt clean -r RX.Y.Z
```
Notes
- The "-r" option follows the command name.
- If you have any local packages (eg. SRT_SITE) that are not in the setup/packages-RX.Y.Z file, you should add them with addpkg or msrt update after the msrt release step.
Normally, msrt will create its own environment by doing the equivalent of srt_setup internally. If you want to use your already existing environment use:
```
    msrt -e <command> <command options>
```
This option overrides some commmand options (ie. "-r <release-name>)."
Convert from one CVS repository access method to another. For example, convert MINOS read-only to read-write.
```
    msrt migrate [optional list of packges]
```
You will still need to arrange for proper CVS/SSH access. See WebDocs/cvs-rep.html
Note: technically, you should never need to convert your base release from read-only to read-write because you are supposed to never directly edit base release files, but instead check out packages into your test release area and commit them from there. In spite of that, many find it convenient to directly edit code in and commit from the base release.
Make cmd line options default. You can use $HOME/.msrtrc to specify default options as well do fancier things. See the documentation in msrt help. You can also see an example .msrtrc file.

Contact

Please contact me, bv@bnl.gov, with any problems, suggestions or comments.

Last Modified: $Date: 2009/01/20 19:39:51 $