Below are three example package definitions. These illustrate some of the more common types of packages. In many case these can be used as is with changes to the package name, revision and home fields.
The figure below illustrates the configuration for the IDL based EUVIMTOOL application.
NOTE 1: The DEPENDENCY LIST only contains the UDFTOIDL package. You might expect the UDFCORE packages to be there also but UDFTOIDL has both a WINDOWS and NON-WINDOWS installation. The WINDOWS installation does not require the UDFCORE packages and the NON-WINDOWS installation does. By just listing a dependency on UDFTOIDL we let UDFTOIDL take care of any dependences it has which removes any OS dependency from this package.
The figure below illustrates the configuration for the documentation for the EUVSim package.
NOTE 1:All document packages should include D,DocBase in the dependency list. This package includes the UDF document style sheets and the documentation index file.
NOTE 2:You should include a revision number with the D,DocBase dependency. This should be set to have a release number 1 higher than the current release. You will need to notify the UDF archive administrator and have an entry added to the table of contents file to include this document. Give as info, the document HOME directory, a title, the file to point to, and the DocBase version number the update should have.
The figure below illustrages the configuration for the Tcl based package TCLUTILS.
NOTE 1: This package contains associated C code evident by the inclusion of the C-Code subdirectory. If the package is pure Tcl with no C code then the package definition should not include the C-Code subdirectory, should not include the C-Code based files in the File Manifest, and does not use a special installer.
NOTE 2: All Tcl based packages need T,TCLCNTRL as a dependency.