1 |
dashley |
23 |
<html> |
2 |
|
|
|
3 |
|
|
<head> |
4 |
|
|
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> |
5 |
|
|
<meta name="GENERATOR" content="Microsoft FrontPage 4.0"> |
6 |
|
|
<meta name="ProgId" content="FrontPage.Editor.Document"> |
7 |
|
|
<title>ESRG Download Release Policy</title> |
8 |
|
|
<base target="main"> |
9 |
|
|
</head> |
10 |
|
|
|
11 |
|
|
<body background="../../bkgnds/bk10.gif"> |
12 |
|
|
|
13 |
|
|
<p align="center"><b><font size="4">ESRG Download Release Policy</font></b></p> |
14 |
|
|
<hr> |
15 |
|
|
<p>As mentioned <a href="../version_nums/vn_policy.htm">here</a>, each release |
16 |
|
|
is "all or nothing". Each release will be assigned a new version |
17 |
|
|
number, and then all of the following files will be released at the same |
18 |
|
|
time. In the following table, <i> <v_n></i> means the version number as |
19 |
|
|
described <a href="../version_nums/vn_policy.htm">here</a> with all dots |
20 |
|
|
replaced by underscores and all letters lower-case.</p> |
21 |
|
|
<div align="center"> |
22 |
|
|
<center> |
23 |
|
|
<table border="2" width="100%"> |
24 |
|
|
<tr> |
25 |
|
|
<td width="33%"><b><u>Release</u></b></td> |
26 |
|
|
<td width="33%"><b><u>Release Format</u></b></td> |
27 |
|
|
<td width="34%"><b><u>Naming Convention</u></b></td> |
28 |
|
|
</tr> |
29 |
|
|
<tr> |
30 |
|
|
<td width="33%"><b>Windows® Tool Set</b></td> |
31 |
|
|
<td width="33%"><a href="../../glossary/glossary.htm#installshield_express">InstallShield |
32 |
|
|
Express</a> installation executable.</td> |
33 |
|
|
<td width="34%"><b>esrg_win_ts_<v_n>.exe</b> |
34 |
|
|
<p><i>Example:</i><br> |
35 |
|
|
<i>esrg_win_ts_1_07_09.exe</i>.</p> |
36 |
|
|
</td> |
37 |
|
|
</tr> |
38 |
|
|
<tr> |
39 |
|
|
<td width="33%"><b>Windows® Tool Set Source Code</b></td> |
40 |
|
|
<td width="33%"><a href="../../glossary/glossary.htm#tar_gz_file">.tar.gz |
41 |
|
|
file</a> with EOL characters of text files converted to Windows format |
42 |
|
|
so that files can be used directly on a Windows® system after |
43 |
|
|
decompression with <a href="http://www.winzip.com">WinZip</a> or a |
44 |
|
|
similar utility.</td> |
45 |
|
|
<td width="34%"><b>esrg_win_ts_src_<v_n>.tar.gz</b> |
46 |
|
|
<p>(See example of file name above for Windows® tool set.)</p> |
47 |
|
|
</td> |
48 |
|
|
</tr> |
49 |
|
|
<tr> |
50 |
|
|
<td width="33%"><b>*nix Tool Set</b></td> |
51 |
|
|
<td width="33%"><a href="../../glossary/glossary.htm#tar_gz_file">.tar.gz |
52 |
|
|
file</a> containing source code and build files, with EOL characters in |
53 |
|
|
*nix format (since the source code will be compiled on a *nix |
54 |
|
|
system). </td> |
55 |
|
|
<td width="34%"><b>esrg_nix_ts_<v_n>.tar.gz</b> |
56 |
|
|
<p>(See example of file name above for Windows® tool set.)</p> |
57 |
|
|
</td> |
58 |
|
|
</tr> |
59 |
|
|
<tr> |
60 |
|
|
<td width="33%"><b>Book "<i>A Practitioner's Guide ...</i>"</b></td> |
61 |
|
|
<td width="33%">.pdf file.</td> |
62 |
|
|
<td width="34%"><b>esrg_ubka_<v_n>.pdf</b> |
63 |
|
|
<p>(See example of file name above for Windows® tool set.)</p> |
64 |
|
|
</td> |
65 |
|
|
</tr> |
66 |
|
|
<tr> |
67 |
|
|
<td width="33%"><b>Book "<i>A Practitioner's Guide ...</i>" |
68 |
|
|
Source Code</b></td> |
69 |
|
|
<td width="33%"><a href="../../glossary/glossary.htm#tar_gz_file">.tar.gz |
70 |
|
|
file</a> with EOL characters of text files converted to Windows format |
71 |
|
|
so that files can be used directly on a Windows® system after |
72 |
|
|
decompression with <a href="http://www.winzip.com">WinZip</a> or a |
73 |
|
|
similar utility.</td> |
74 |
|
|
<td width="34%"><b>esrg_ubka_src_<v_n>.pdf</b> |
75 |
|
|
<p>(See example of file name above for Windows® tool set.)</p> |
76 |
|
|
</td> |
77 |
|
|
</tr> |
78 |
|
|
<tr> |
79 |
|
|
<td width="33%"><b>Embedded System Libraries</b></td> |
80 |
|
|
<td width="33%"><a href="../../glossary/glossary.htm#tar_gz_file">.tar.gz |
81 |
|
|
file</a> with EOL characters of text files converted to Windows format |
82 |
|
|
so that files can be used directly on a Windows® system after |
83 |
|
|
decompression with <a href="http://www.winzip.com">WinZip</a> or a |
84 |
|
|
similar utility.</td> |
85 |
|
|
<td width="34%"><b>esrg_eslib_<v_n>.pdf</b> |
86 |
|
|
<p>(See example of file name above for Windows® tool set.)</p> |
87 |
|
|
</td> |
88 |
|
|
</tr> |
89 |
|
|
<tr> |
90 |
|
|
<td width="33%"><b>RTOS's, Kernels, Schedulers, And Integrated Software |
91 |
|
|
Components</b></td> |
92 |
|
|
<td width="33%"><a href="../../glossary/glossary.htm#tar_gz_file">.tar.gz |
93 |
|
|
file</a> with EOL characters of text files converted to Windows format |
94 |
|
|
so that files can be used directly on a Windows® system after |
95 |
|
|
decompression with <a href="http://www.winzip.com">WinZip</a> or a |
96 |
|
|
similar utility.</td> |
97 |
|
|
<td width="34%"><b>esrg_rtos_<v_n>.tar.gz</b> |
98 |
|
|
<p>(See example of file name above for Windows® tool set.)</p> |
99 |
|
|
</td> |
100 |
|
|
</tr> |
101 |
|
|
<tr> |
102 |
|
|
<td width="33%"><b>PHP Library</b></td> |
103 |
|
|
<td width="33%"><a href="../../glossary/glossary.htm#tar_gz_file">.tar.gz |
104 |
|
|
file</a> with EOL characters in *nix format (since the PHP scripts will |
105 |
|
|
be used on a *nix server).</td> |
106 |
|
|
<td width="34%"><b>esrg_phpa_<v_n>.tar.gz</b> |
107 |
|
|
<p>(See example of file name above for Windows® tool set.)</p> |
108 |
|
|
</td> |
109 |
|
|
</tr> |
110 |
|
|
<tr> |
111 |
|
|
<td width="33%"><b>Web Content</b></td> |
112 |
|
|
<td width="33%"><a href="../../glossary/glossary.htm#tar_gz_file">.tar.gz |
113 |
|
|
file</a> with EOL characters of text files in *nix format (since the web |
114 |
|
|
content will be used on a *nix server).</td> |
115 |
|
|
<td width="34%"><b>esrg_weba_<v_n>.tar.gz</b> |
116 |
|
|
<p>(See example of file name above for Windows® tool set.)</td> |
117 |
|
|
</tr> |
118 |
|
|
</table> |
119 |
|
|
</center> |
120 |
|
|
</div> |
121 |
|
|
<p><b><u>Additional Notes:</u></b></p> |
122 |
|
|
<ol> |
123 |
|
|
<li>The majority of the release files cited above are prepared on <a href="http://sourceforge.net">SourceForge</a>'s shell servers using a single script. This is done to |
124 |
|
|
ease the burden of data transfer over a modem connection. At this time |
125 |
|
|
only the book <i> .PDF</i> file requires preparation on a Windows® |
126 |
|
|
platform.</li> |
127 |
|
|
<li>There are some materials not packaged above. These |
128 |
|
|
materials are: |
129 |
|
|
<ul> |
130 |
|
|
<li>*nix scripts and other files used to build the file releases |
131 |
|
|
enumerated above (these are contained in the CVS module "<i>esrgdsts</i>").</li> |
132 |
|
|
<li><a href="../../glossary/glossary.htm#installshield_express" target="_blank">InstallShield |
133 |
|
|
Express</a> files, bitmap images, icons, etc. which are necessary to |
134 |
|
|
build the Windows® installation executable (these are contained in the |
135 |
|
|
CVS module "<i>esrgdstb</i>").</li> |
136 |
|
|
</ul> |
137 |
|
|
Note that these materials are only available via anonymous CVS. |
138 |
|
|
</li> |
139 |
|
|
<li>Because of the preparation on a foreign platform (<a href="../../glossary/glossary.htm#tar_gz_file" target="_blank">.tar.gz |
140 |
|
|
files</a> of source code to be used |
141 |
|
|
on a Windows® platform are prepared on a *nix platform), there must be |
142 |
|
|
rules for the naming of text files so that the <i>unix2dos</i> utility will |
143 |
|
|
be invoked only on text files. It may be instructive to review these |
144 |
|
|
rules, arranged by CVS module.</li> |
145 |
|
|
</ol> |
146 |
|
|
<hr> |
147 |
|
|
<p align="center" style="margin-top: -2; margin-bottom: -1"><font size="1">This |
148 |
|
|
web page is maintained by <a href="mailto:dtashley@users.sourceforge.net">David |
149 |
|
|
T. Ashley</a>.<br>$Header: /cvsroot/esrg/sfesrg/esrgweba/htdocs/devels/dwn_rel_policy/dwn_rel_policy.htm,v 1.3 2003/04/27 08:11:07 dtashley Exp $</font></p> |
150 |
|
|
<hr noshade size="5"> |
151 |
|
|
|
152 |
|
|
</body> |
153 |
|
|
|
154 |
|
|
</html> |