| 49 |
|
dependent on the project configuration. There is currently no easy way of |
| 50 |
|
providing online help as to exactly what this is without relying on the |
| 51 |
|
project administrator to document it carefully. |
| 52 |
– |
<p> |
| 53 |
– |
Future developments aim to improve this interface, and move more |
| 54 |
– |
functionality to the scram command where it is only currently |
| 55 |
– |
available via less straightforward means (e.g. editing files). |
| 52 |
|
</td> |
| 53 |
|
</tr> |
| 54 |
|
<tr> |
| 74 |
|
Once it is tested and the tool is to be made available to the entire project, |
| 75 |
|
its name/url should be added to the 'project requirements' file via the |
| 76 |
|
<Require > tag.<br> |
| 81 |
– |
<em>Current limitations</em><br> |
| 82 |
– |
The url mechanism is limited to a simple toolname which corresponds to a file |
| 83 |
– |
in the current SCRAM toolbox area. A scram setup can only be performed once |
| 84 |
– |
for any specific file without strange results.<br> |
| 85 |
– |
Future developments will allow any url (e.g file:, http:) to be specified. |
| 86 |
– |
This will allow description files to be stored anywhere on the net for use |
| 87 |
– |
between different projects that use the same external product. |
| 77 |
|
<p> |
| 78 |
|
Specifying a product to be used once its installed can be done via the |
| 79 |
< |
BuildFile and a special <External name=<em>toolname</em>> tag. This will |
| 91 |
< |
soon be depreciated to simplyfy the interface to be replaced with the |
| 92 |
< |
<Use external=> tag. |
| 79 |
> |
BuildFile and a special <External name=<em>toolname</em>> tag. |
| 80 |
|
</td> |
| 81 |
|
</tr> |
| 82 |
|
<tr> |
| 83 |
|
<td> |
| 84 |
|
<li> |
| 85 |
< |
SRT shall obtain required build objects in the most efficient manner |
| 85 |
> |
Shall obtain required build objects in the most efficient manner |
| 86 |
|
</td> |
| 87 |
|
<td> |
| 88 |
|
This requirement really |
| 136 |
|
</td> |
| 137 |
|
<td> |
| 138 |
|
Multiple platforms are supported. Choice of compilers etc. is made at the |
| 139 |
< |
project level. Compiler types/QA tool are currently hardcoded in although |
| 140 |
< |
future developments will require a tool description file for each |
| 154 |
< |
so that any such tool can be easily installed/used with the scram setup |
| 155 |
< |
command as with any other external product. |
| 139 |
> |
project level. Compiler types/QA tools can be included with a Tool description |
| 140 |
> |
file. |
| 141 |
|
</td> |
| 142 |
|
</tr> |
| 143 |
|
<tr> |
| 359 |
|
<tr> |
| 360 |
|
<td> |
| 361 |
|
<li> |
| 362 |
< |
More than one version of SRT must be able to reside on any given |
| 362 |
> |
More than one version of SCRAM must be able to reside on any given |
| 363 |
|
"site" at the same time. |
| 364 |
|
</td> |
| 365 |
|
<td> |
| 385 |
|
class can be easily interchanged. (e.g repository management software) |
| 386 |
|
<p> |
| 387 |
|
<li> |
| 388 |
< |
SRT shall have "project" specific selection of any "tools" |
| 388 |
> |
SCRAM shall have "project" specific selection of any "tools" |
| 389 |
|
and "external software" (including version specification). |
| 390 |
< |
(e.g. Compilers, Package Management, libraries, repository, SRT Version) |
| 390 |
> |
(e.g. Compilers, Package Management, libraries, repository, |
| 391 |
> |
SCRAM Version) |
| 392 |
|
</td> |
| 393 |
|
<td> |
| 394 |
|
Yes with tool description files/ project files and no dependence on any |
| 399 |
|
<td> |
| 400 |
|
<li> |
| 401 |
|
provide an automatic installation procedure for any |
| 402 |
< |
SRT maintained project |
| 402 |
> |
SCRAM maintained project |
| 403 |
|
</td> |
| 404 |
|
<td> |
| 405 |
|
Just click on a web page to install the project! |
| 461 |
|
<tr> |
| 462 |
|
<td> |
| 463 |
|
<li> |
| 464 |
< |
SRT must provide a mechanism to specify "external software" |
| 464 |
> |
SCRAM must provide a mechanism to specify "external software" |
| 465 |
|
requirements and default configurations. |
| 466 |
|
<p> |
| 467 |
|
<li> |
| 481 |
|
Yes - individual projects are self contained. |
| 482 |
|
</td> |
| 483 |
|
</tr> |
| 484 |
+ |
<tr> |
| 485 |
+ |
<td> |
| 486 |
+ |
User must be able to see the project resources made available |
| 487 |
+ |
through SCRAM |
| 488 |
+ |
</td> |
| 489 |
+ |
<td> |
| 490 |
+ |
Once a project is installed it is entered into a SCRAM database. The |
| 491 |
+ |
<em>scram list</em> command will show all the available projects installed |
| 492 |
+ |
which are available to the user. SCRAM also allows database linking so that |
| 493 |
+ |
scram project installations on remote sites can |
| 494 |
+ |
also be made available over a shared file system. |
| 495 |
+ |
</td> |
| 496 |
+ |
</tr> |
| 497 |
|
</table> |
| 498 |
|
|
| 499 |
|
<! Style Sheet Footer ---------------Do not change anything after this line--> |
| 504 |
|
>Chris Williams</a> |
| 505 |
|
</td> |
| 506 |
|
<td align=center> |
| 507 |
< |
Last Updated Tue Apr 20 15:08:35 1999 |
| 507 |
> |
Last Updated Tue Aug 22 16:37:41 2000 |
| 508 |
|
</td> |
| 509 |
|
<td align=right><a href=/cgi-cmc/pagestat>Show Stats</a> |
| 510 |
|
</td> |
