Release 7.1.0 Software notes

Documentation and SCOhelp

NOTE: For other Netscape Communicator errors, see ``Internet and Intranet''.

Running SCOhelp from the CDE desktop

To run SCOhelp from the CDE desktop in a non-C locale, select it from the CDE menu. Do not start it from the default dtterm terminal window. This limitation does not apply to the Panorama desktop or the C locale.

config_man errors on re-indexing SCOhelp

When you install the UnixWare 7 Release 7.1 documentation packages, in particular the BASEman package, and then attempt to create the search index using config_search, you will see multiple harmless errors on the command's invocation.

This is caused by the command attempting to process files for manual page sections that are no longer included in UnixWare 7.

If you do not want these errors to display, remove the following files before running config_search:

/usr/lib/scohelp/en_US.ISO8859-1/_SearchIndex/Insert/man.1Mxnx.vbi
/usr/lib/scohelp/en_US.ISO8859-1/_SearchIndex/Insert/man.1xnx.vbi
/usr/lib/scohelp/en_US.ISO8859-1/_SearchIndex/Insert/man.2xnx.vbi
/usr/lib/scohelp/en_US.ISO8859-1/_SearchIndex/Insert/man.4xnx.vbi
/usr/lib/scohelp/en_US.ISO8859-1/_SearchIndex/Insert/man.X3xi.vbi

Documentation errata - multiple package instances

The UnixWare 7 documentation incorrectly states that the $PKGINST parameter is used to track multiple installations of a package installed using the same package abbreviation (PKG), by appending a number to the PKGINST parameter value, and incrementing the number with each successive package installation. Thus, the second installation of a package called ``package'' sets PKGINST for that package to ``package.1'', and so on with successive installations of the package. It goes on to state that, subsequently, using this identifier, each instance can be removed from the system independently of any other instances. This mechanism does not work.

There are two ways to work around this:

You can manually increment the PKG and PKGINST parameters in your pkginfo(4) file and installation scripts to use this incremental naming scheme. <P> For example, you create a package whose package abbreviation (the PKG parameter) is ``package''. You install the package (using the pkgadd(1M) utility). Then, you create a second image of the package called ``package.1'', and install that version. This provides a variant of the package instance handling functionality described in the documentation, because the package abbreviations (PKG) are different. When you use pkginfo to display the installed packages, it will show both ``package'' and ``package.1'' as installed. These ``instances'' of the package can then be removed individually (usually, in reverse order). This dependency can be accounted for in the installation scripts, by requiring that ``package'' is already installed in the system. This can be done in the depend installation file. This also prevents ``package'' from being removed before ``package.1''. Your package installation scripts should set PKGINST to the same value as PKG.
You can simply create new versions of an existing package with the same PKG and PKGINST values, but different parameters (such as VERSION and DESC) in the pkginfo file. Doing so simply overlays a new version of the same package over the older version. A pkginfo with no options shows only ``package'' as being installed. A pkginfo -l package command, however, will show the updated values of the VERSION parameter (and any other changed pkginfo parameters) changed by the installation of the new version of the package.
When the package is removed with pkgrm(1M), all files belonging to all installed versions of the package are removed, and the package will no longer appear in the pkginfo list.
Care should be taken when using this method to manage file deletions and package dependencies. You must be sure that the request or preinstall scripts for all versions of such packages do not specifically prevent the installation of a package with the same name, or reinstalling the same package again (over itself).

Accordingly, the following modifications should be made to the online documentation topic Software Development Software Development Tools Packaging your Software Applications . References to the automatic incrementing of PKGINST during installation of packages with the same package abbreviation should be ignored in these sections:

``Installation Parameters''
``Step 2. Defining a Package Instance''

Errors when installing BASEdoc over Release 7.0.1

Installing the UnixWare 7 Release 7.1.0 version of the BASEdoc package may result in some error messages during file installation, and a ``partially failed'' installation result (which is also observable using pkginfo -l BASEdoc from the command line after installation). This is due to the removal of files from the BASEdoc package that now appear in another package. Ignore these error messages and the ``partially failed'' result. The documentation will be correctly re-configured during the BASEdoc postinstall script, and these errors will not be seen again during a subsequent installation or re-configuration of documentation packages.

Installing troff man pages

If you install any raw man pages, that is, man pages that are coded with the man troff macros, then you must have the BSDcompat package installed first. That is because such pages require nroff, which is in BSDcompat.

After installing the BSDcompat package, include /usr/ucb in the PATH variable if you want to run catman to process unformatted man pages from the root.

Running SCOhelp as root on the system console

When you run communicator(X1) or scohelp(X1) as root on the system console, Netscape Communicator sets:

xhost +local:

This enables non-networked local connections to your X server, but also might allow other users logged into the system to make windows pop up on your screen without your permission.

To correct this, after exiting communicator or scohelp, enter:

xhost -local:

config_search console errors

After you install UnixWare 7, Release 7.1, you might see errors generated by config_search(1M). These errors are generated by config_search when it tries to index files removed by the Release 7.1 update. The error messages are harmless and do not affect the validity of the index.

SCOhelp: using Back button when searching

Using the Back button in the SCOhelp frame to return to the first page of search results causes an error. This is harmless, and may be ignored. You may wish to redo the search.