| 227 |
dpurdie |
1 |
JATS Installation Process
|
|
|
2 |
-------------------------
|
|
|
3 |
|
|
|
4 |
1) Place the JATS package in a suitable directory
|
|
|
5 |
|
|
|
6 |
2) Perform the host-specific installation operation
|
|
|
7 |
SOLARIS: run the script PostInstall.sh
|
|
|
8 |
WINDOWS: do nothing
|
|
|
9 |
|
|
|
10 |
3) Tailor the JATS startup script
|
|
|
11 |
SOLARIS: tailor TOOLS/jats.sh
|
|
|
12 |
LINUX: tailor TOOLS/jats.sh
|
|
|
13 |
WINDOWS: tailor TOOLS/jats.bat
|
|
|
14 |
|
|
|
15 |
The JATS startup script may be copied to a directory within the users
|
|
|
16 |
PATH and the various values within the script may be alterred to suite
|
|
|
17 |
the users environment.
|
|
|
18 |
|
|
|
19 |
The JATS startup script may be modified in-situ and the users PATH
|
|
|
20 |
extended to include the TOOLS directory.
|
|
|
21 |
|
|
|
22 |
The JATS startup script is designed to need no changes from JATS
|
|
|
23 |
release to JATS release. Its sole purpose is to startup another
|
|
|
24 |
JATS script that is contained within the release.
|
|
|
25 |
|
|
|
26 |
|
|
|
27 |
JATS Requirements
|
|
|
28 |
-----------------
|
|
|
29 |
|
|
|
30 |
1) Perl 5.6.1 or better
|
|
|
31 |
2) Compilers and tools as required by the targets being built
|
|
|
32 |
|
|
|
33 |
========================================================================
|
|
|
34 |
|
|
|
35 |
Host-specific Installation Operation
|
|
|
36 |
-----------------------------------
|
|
|
37 |
|
|
|
38 |
SOLARIS and LINUX (Done by PostInstall.sh)
|
|
|
39 |
1) Make the scripts in TOOLS executable
|
|
|
40 |
2) Make the binaries in BIN.xxx executable as required
|
|
|
41 |
3) Untar the links.tar file in BIN.xxx as required
|
|
|
42 |
|
|
|
43 |
WINDOWS
|
|
|
44 |
Nothing
|
|
|
45 |
|
|
|
46 |
========================================================================
|
|
|
47 |
========================================================================
|
|
|
48 |
|
|
|
49 |
Creating the JATS package for Release
|
|
|
50 |
-------------------------------------
|
|
|
51 |
|
|
|
52 |
1) Make changes to the JATS files
|
|
|
53 |
Clearcase config Spec:
|
|
|
54 |
element /MASS_Dev_Infra/... .../mass_dev/LATEST
|
|
|
55 |
element /MASS_Dev_Infra/... /main/LATEST
|
|
|
56 |
load /MASS_Dev_Infra/core_devl
|
|
|
57 |
|
|
|
58 |
2) Update the ChangeLog.txt file
|
|
|
59 |
|
| 229 |
dpurdie |
60 |
3) Label ALL files in the core_devl view with the JATS_XX.XX.XX.cr label
|
| 227 |
dpurdie |
61 |
|
| 229 |
dpurdie |
62 |
4) Use the jats command:
|
|
|
63 |
jats release JATS_XX.XX.XX.cr
|
|
|
64 |
to release the package.
|
| 227 |
dpurdie |
65 |
|
| 229 |
dpurdie |
66 |
5) On "auperaunx26", locate the released package and run the PostInstall script.
|
| 227 |
dpurdie |
67 |
cd core_devl/XX.XX.XX.cr
|
|
|
68 |
./PostInstall.sh
|
|
|
69 |
|
| 229 |
dpurdie |
70 |
6)Update the softlink to the latest version of JATS
|
| 227 |
dpurdie |
71 |
On "auperaunx26", in the directory /devl
|
|
|
72 |
|
|
|
73 |
rm core_devl2
|
| 229 |
dpurdie |
74 |
ln -s dpkg_archive/core_devl/XX.XX.XX.cr core_devl2
|
| 227 |
dpurdie |
75 |
|
| 229 |
dpurdie |
76 |
7) Maintain the Release Manager Entry
|
|
|
77 |
|
|
|
78 |
8) Email the last release note entry to all
|