|
Eloquence patches are provided to either fix a defect or limitation
that was found after release and/or to add new functionality.
For an overview on available patches, please refer to the Eloquence B.07.00
patch overview document.
Eloquence patches are typically included in a subsequent release or distribution.
Patches are provided as compressed tar (on HP-UX and Linux) or zip archives (on Windows).
Eloquence B.07.00 patch file names have a format as shown below:
PE70-0304041-hpux-ia64.tar.gz
^ ^ ^
| | Architecture
| Operating system
Patch id
The patch id consists of two digits year, month and day and an additional digit
to distinguish multiple patches released on the same day.
The operating system specifies the operating system and architecture either
hardware dependencies or a specific distribution.
A README file is provided for each patch that describes the fixed problems,
installation instructions and affected files. The README file on the ftp server
uses UNIX conventions (line feed as a line separator) and can be opened on Windows
using the Eloquence IDE or the Windows WordPad application.
Patches should be installed in ascending order and are usually cumulative
and include the replaced patches. The following information is included
in a patch description:
- Severity - One of NEW FUNCTIONALITY, BUG FIX or CRITICAL.
CRITICAL patches should always be installed as they might fix a possible data
corruption problem.
- Platforms - All or a list of affected operating systems
- List of replaced patches (if any)
On HP-UX and Linux, Eloquence patches are relative to the /opt/eloquence6
directory. The Windows zip archives do not include path information.
Eloquence "beta" patches are used to release optional patches (eg. new
functionality or non-critical fixes) or new patches. New patches may be
moved to the main patch directory after receiving positive feedback.
HP-UX
To install the patch you need to uncompress and unpack it with gzip
and tar. The gzip utility is included with HP-UX 10.x and above.
Installation requires root privileges.
cd /opt/eloquence6
gzip -dc /path/to/PE70-<id>-hpux-<arch>.tar.gz | tar xf -
Where <id> is the patch id (such as 0304041) and <arch>
is the patch architecture (such as pa20). The architecture should be
equivalent to the Eloquence distribution that was installed initially.
The following architectures are supported with Eloquence B.07.00:
- pa11 - PA-RISC 1.1
- pa20 - PA-RISC 2.0 (32 and 64 bit HP-UX)
- ia64 - Itanium
HP-UX patches include a README file that is placed in the
share/doc subdirectory for later reference.
Linux
To install the patch you need to uncompress and unpack it with tar.
Installation requires root privileges.
cd /opt/eloquence6
tar xzf /path/to/PE70-<id>-linux-<arch>.tar.gz
Where <id> is the patch id (such as 0304041) and <arch>
is the patch architecture (such as glibc2.2). The architecture should be
equivalent to the Eloquence distribution that was installed initially.
The following architectures are supported with Eloquence B.07.00:
- glibc2.1 - glibc2.1 based Linux distribution
- glibc2.2 - glibc2.1 based Linux distribution
- rh8 - RedHat 8
Linux patches include a README file which is placed in the
share/doc subdirectory for later reference.
Windows
Windows patches are provided as self-extracting executables which automatically
install the contained patch files to the appropriate directories.
This was introduced on 14. July 2004. Previously, Windows patches were provided
as zip archives and required manual installation of the contained files. For a
transitional period, these zip archives are provided in addition. Each of these
archives include a README file which contains detailed instructions about how
the patch files must be installed.
Windows patches include a README file which is placed in the
share/doc subdirectory for later reference.
|
