| 16 |
|
You will be asked questions about your system as required by the project during |
| 17 |
|
the installation. Some error and consistency checking is provided |
| 18 |
|
(but is still in its infancy so dont expect anything too fancy). |
| 19 |
+ |
You can change these values later (see below) |
| 20 |
+ |
so dont worry too much if you get things wrong at this stage. |
| 21 |
|
<p> |
| 22 |
|
Once through the installation process you can make the project available for |
| 23 |
|
general use by using the <em>cvs install</em> command. This command will |
| 24 |
|
update your local SCRAM database with the project details so that other |
| 25 |
|
SCRAM user can simply refer to it by name. |
| 26 |
|
<p> |
| 27 |
+ |
<h2>Changing Installation Defaults</h2> |
| 28 |
+ |
You can use the <P> |
| 29 |
+ |
<b>scram setup <em>toolname</em></b><p> |
| 30 |
+ |
command to rerun the installation of a specific tool.<p> |
| 31 |
+ |
At present there is no easy way to override the automatic mechanisms that |
| 32 |
+ |
SCRAM uses to install a tool - so if the setup command is not sufficient you |
| 33 |
+ |
can modify the values directly. Simply edit the "clientsettings" file |
| 34 |
+ |
in the .SCRAM/<em>architecture_specific</em> directory from the top of the |
| 35 |
+ |
project installation. |
| 36 |
|
<! Style Sheet Footer ---------------Do not change anything after this line--> |
| 37 |
|
<hr> |
| 38 |
|
<table border=1 width=100%> |
