| 1 |
williamc |
1.1 |
<! Style Sheet Header>
|
| 2 |
|
|
<html>
|
| 3 |
|
|
<head>
|
| 4 |
|
|
<title>project.html</title>
|
| 5 |
williamc |
1.2.2.3 |
<body bgcolor=beige>
|
| 6 |
williamc |
1.1 |
<! End Style Sheet Header -----------Insert Text Here --------------------->
|
| 7 |
|
|
<center>
|
| 8 |
|
|
<h1>Installing a Project Using SCRAM</h1>
|
| 9 |
williamc |
1.2.2.3 |
<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 |
williamc |
1.1 |
</center>
|
| 13 |
|
|
<hr>
|
| 14 |
williamc |
1.2.2.2 |
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 |
williamc |
1.1 |
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
|
| 24 |
|
|
process.
|
| 25 |
|
|
<p>
|
| 26 |
|
|
You will be asked questions about your system as required by the project during
|
| 27 |
|
|
the installation. Some error and consistency checking is provided
|
| 28 |
|
|
(but is still in its infancy so dont expect anything too fancy).
|
| 29 |
williamc |
1.2.2.1 |
You can change these values later (see below)
|
| 30 |
|
|
so dont worry too much if you get things wrong at this stage.
|
| 31 |
williamc |
1.1 |
<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
|
| 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 |
williamc |
1.2 |
<h2>Changing Installation Defaults</h2>
|
| 38 |
williamc |
1.2.2.1 |
You can use the <P>
|
| 39 |
williamc |
1.2.2.3 |
<b>scram setup [-i] <em>toolname [[version] [file]]</em></b><p>
|
| 40 |
williamc |
1.2.2.1 |
command to rerun the installation of a specific tool.<p>
|
| 41 |
williamc |
1.2.2.3 |
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 |
williamc |
1.2 |
in the .SCRAM/<em>architecture_specific</em> directory from the top of the
|
| 47 |
|
|
project installation.
|
| 48 |
williamc |
1.1 |
<! Style Sheet Footer ---------------Do not change anything after this line-->
|
| 49 |
|
|
<hr>
|
| 50 |
|
|
<table border=1 width=100%>
|
| 51 |
|
|
<td align=left>
|
| 52 |
|
|
<a href=mailto:Christopher.Williams@cern.ch
|
| 53 |
|
|
>Chris Williams</a>
|
| 54 |
|
|
</td>
|
| 55 |
|
|
<td align=center>
|
| 56 |
|
|
<script language="JavaScript">
|
| 57 |
|
|
<!---//hide script from old browsers
|
| 58 |
|
|
document.write( "<br>Last updated "+ document.lastModified
|
| 59 |
|
|
);
|
| 60 |
|
|
//end hiding contents --->
|
| 61 |
|
|
</script>
|
| 62 |
|
|
</td>
|
| 63 |
|
|
<td align=right>Show <a href=/cgi-cmc/pagestat>Stats</a>
|
| 64 |
|
|
</td>
|
| 65 |
|
|
</table>
|
| 66 |
|
|
</body> </html>
|
| 67 |
|
|
<! End Style Sheet Footer>
|
