| 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 |
|
|
|
60 |
3) Update the file "jats.pl" with the next release version number - XX.XX.XX
|
|
|
61 |
The string $GBE_VERSION is checked in a later step and must be updated.
|
|
|
62 |
|
|
|
63 |
4) Label ALL files in the core_devl view with the JATS_XX.XX.XX label
|
|
|
64 |
|
|
|
65 |
5) Create a view based on the label
|
|
|
66 |
|
|
|
67 |
6) Within the created view, locate the BUILD directory and run the
|
|
|
68 |
'MakePackage.pl' script. ie:
|
|
|
69 |
|
|
|
70 |
perl MakePackage.pl XX.XX.XX
|
|
|
71 |
|
|
|
72 |
7) Release the generated package image to dpkg_archive with the command
|
|
|
73 |
jats -here create_dpkg
|
|
|
74 |
|
|
|
75 |
8) Remove the view
|
|
|
76 |
|
|
|
77 |
9) On "auperaunx26", locate the released package and run the PostInstall script.
|
|
|
78 |
cd core_devl/XX.XX.XX.cr
|
|
|
79 |
./PostInstall.sh
|
|
|
80 |
|
|
|
81 |
10)Update the softlink to the latest version of JATS
|
|
|
82 |
On "auperaunx26", in the directory /devl
|
|
|
83 |
|
|
|
84 |
rm core_devl2
|
|
|
85 |
ln -s dpkg_archive/core_devl/2.52.2.cr core_devl2
|
|
|
86 |
|
|
|
87 |
11)Update build machines as required
|
|
|
88 |
|
|
|
89 |
12) Email the last release note entry to all
|