8 |
|
<h1>Installing a Project Using SCRAM</h1> |
9 |
|
</center> |
10 |
|
<hr> |
11 |
+ |
It is envisaged that releases of a project need to be distributed to remote |
12 |
+ |
sites. The release is contained in a special scram area which is created |
13 |
+ |
by scram according to the projects requirements. Once a carbon copy of the area |
14 |
+ |
has been built on the remote site, the adminisatrator can "scram install" it |
15 |
+ |
into the remote sites scram database. Once installed many other scram |
16 |
+ |
development areas can be based upon it, for use both other users,developers etc. |
17 |
+ |
<p> |
18 |
|
SCRAM aims to make installion of projects as painless a possible. |
19 |
|
It is designed to be used |
20 |
|
with a web browser so that you simply click on a link to start the installation |
23 |
|
You will be asked questions about your system as required by the project during |
24 |
|
the installation. Some error and consistency checking is provided |
25 |
|
(but is still in its infancy so dont expect anything too fancy). |
26 |
+ |
You can change these values later (see below) |
27 |
+ |
so dont worry too much if you get things wrong at this stage. |
28 |
|
<p> |
29 |
|
Once through the installation process you can make the project available for |
30 |
|
general use by using the <em>cvs install</em> command. This command will |
32 |
|
SCRAM user can simply refer to it by name. |
33 |
|
<p> |
34 |
|
<h2>Changing Installation Defaults</h2> |
35 |
< |
At present there is no nice interface to change any settings once made. You |
36 |
< |
can however modify the values directly. Simply edit the "clientsettings" file |
35 |
> |
You can use the <P> |
36 |
> |
<b>scram setup <em>toolname</em></b><p> |
37 |
> |
command to rerun the installation of a specific tool.<p> |
38 |
> |
At present there is no easy way to override the automatic mechanisms that |
39 |
> |
SCRAM uses to install a tool - so if the setup command is not sufficient you |
40 |
> |
can modify the values directly. Simply edit the "clientsettings" file |
41 |
|
in the .SCRAM/<em>architecture_specific</em> directory from the top of the |
42 |
|
project installation. |
43 |
|
<! Style Sheet Footer ---------------Do not change anything after this line--> |