| 2 |
|
<html> |
| 3 |
|
<head> |
| 4 |
|
<title>project.html</title> |
| 5 |
< |
<body> |
| 5 |
> |
<body bgcolor=beige> |
| 6 |
|
<! End Style Sheet Header -----------Insert Text Here ---------------------> |
| 7 |
|
<center> |
| 8 |
|
<h1>Installing a Project Using SCRAM</h1> |
| 9 |
+ |
<font color=red>S</font>oftware <font color=red>C</font>onfiguration, |
| 10 |
+ |
<font color=red>R</font>elease <font color=red>A</font>nd |
| 11 |
+ |
<font color=red>M</font>anagement |
| 12 |
|
</center> |
| 13 |
|
<hr> |
| 14 |
+ |
It is envisaged that releases of a project need to be distributed to remote |
| 15 |
+ |
sites. The release is contained in a special scram area which is created |
| 16 |
+ |
by scram according to the projects requirements. Once a carbon copy of the area |
| 17 |
+ |
has been built on the remote site, the adminisatrator can "scram install" it |
| 18 |
+ |
into the remote sites scram database. Once installed many other scram |
| 19 |
+ |
development areas can be based upon it, for use both other users,developers etc. |
| 20 |
+ |
<p> |
| 21 |
|
SCRAM aims to make installion of projects as painless a possible. |
| 22 |
|
It is designed to be used |
| 23 |
|
with a web browser so that you simply click on a link to start the installation |
| 30 |
|
so dont worry too much if you get things wrong at this stage. |
| 31 |
|
<p> |
| 32 |
|
Once through the installation process you can make the project available for |
| 33 |
< |
general use by using the <em>cvs install</em> command. This command will |
| 33 |
> |
general use by using the <em>scram install</em> command. This command will |
| 34 |
|
update your local SCRAM database with the project details so that other |
| 35 |
|
SCRAM user can simply refer to it by name. |
| 36 |
|
<p> |
| 37 |
|
<h2>Changing Installation Defaults</h2> |
| 38 |
|
You can use the <P> |
| 39 |
< |
<b>scram setup <em>toolname</em></b><p> |
| 39 |
> |
<b>scram setup [-i] <em>toolname [[version] [file]]</em></b><p> |
| 40 |
|
command to rerun the installation of a specific tool.<p> |
| 41 |
< |
At present there is no easy way to override the automatic mechanisms that |
| 42 |
< |
SCRAM uses to install a tool - so if the setup command is not sufficient you |
| 43 |
< |
can modify the values directly. Simply edit the "clientsettings" file |
| 41 |
> |
You can override the automatic mechanisms that |
| 42 |
> |
SCRAM uses to install a tool with the <b>-i</b> option |
| 43 |
> |
<br> |
| 44 |
> |
If the setup command is not sufficient you |
| 45 |
> |
can modify the values directly. Simply edit the appropriate <em>.dat</em> file |
| 46 |
|
in the .SCRAM/<em>architecture_specific</em> directory from the top of the |
| 47 |
|
project installation. |
| 48 |
|
<! Style Sheet Footer ---------------Do not change anything after this line--> |
