@@ -10,31 +10,25 @@ Rocks rolls from the SDSC development group.
10
10
To build/install this roll you must have root access to a Rocks development
11
11
machine (e.g., a frontend or development appliance).
12
12
13
- If your Rocks development machine does * not* have Internet access you must
14
- download the appropriate R source file(s) using a machine that does have
15
- Internet access and copy them into the ` src/<packages> ` directories on your
16
- Rocks development machine.
17
-
18
13
19
14
## Dependencies
20
15
21
16
None.
22
17
18
+
23
19
## Building
24
20
25
- To build the sdsc-roll, execute these instructions on a Rocks development
21
+ To build the sdsc-roll, execute this on a Rocks development
26
22
machine (e.g., a frontend or development appliance):
27
23
28
24
``` shell
29
25
% make 2>&1 | tee build.log
30
- % grep " RPM build error" build.log
31
26
```
32
27
33
- If nothing is returned from the grep command then the roll should have been
34
- created as... ` sdsc-roll-*.iso ` . If you built the roll on a Rocks frontend then
35
- proceed to the installation step. If you built the roll on a Rocks development
36
- appliance you need to copy the roll to your Rocks frontend before continuing
37
- with installation.
28
+ A successful build will create the file ` weka-*.disk1.iso ` . If you built the
29
+ roll on a Rocks frontend, proceed to the installation step. If you built the
30
+ roll on a Rocks development appliance, you need to copy the roll to your Rocks
31
+ frontend before continuing with installation.
38
32
39
33
40
34
## Installation
@@ -49,3 +43,13 @@ To install, execute these instructions on a Rocks frontend:
49
43
% rocks run roll sdsc | bash
50
44
```
51
45
46
+
47
+ ## Testing
48
+
49
+ The sdsc-roll includes a test script which can be run to verify proper
50
+ installation of the roll documentation, binaries and module files. To
51
+ run the test scripts execute the following command(s):
52
+
53
+ ``` shell
54
+ % /root/rolltests/sdsc.t
55
+ ```
0 commit comments