Previous Next Contents Generated Index Home


Chapter 21

Sun Management Center Developer Environment Packaging




This chapter covers the following topics:

The information provided in this chapter will be based on the packaging of the example modules provided as part of the Developer Environment.

The following documents are suggested reading for more detailed explanation of Solaris software packaging:

This chapter provides examples and a list of suggested Sun Management Center software packaging practices with more details on the configuration of the packaging files.


Packaging Helloworld_01

The following section describes the packaging of the Helloworld_01 module (src/examples/modules/helloworld_01/package).


Makefile

The makefile is set up to look for the components to be packaged in the parent directory of the package directory (src/examples/modules/helloworld_01).

This is accomplished by supplying the pkgmk utility with the
'-r [path_to_components]' option, which in this example is '..':

COMPONENT_ROOT = ..
DEMOeshw1:
$(PKGMK) -o -r $(COMPONENT_ROOT) -d .

The contents of the package are defined in:
src/examples/modules/helloworld_01/package/prototype.


Prototype Entries

Here are the entries in the prototype file and a description of their functions:


Sun Management Center Software Packaging Practices


Package Naming

The Sun Management Center team uses SUNWes to denote that this package is a Sun Microsystems (SUNW) package and belongs to the Enterprise software group of packages. The next three characters are used to identify the individual packages of Sun Management Center software.


Package Versioning

The Sun Management Center team uses the VERSION, REVISION macros with the following form for Solaris software dependent packages (OS equals Solaris Release, note that 2.5.1 would be 2.5:, that is, Major.Minor, not Major.Minor.Micro):

VERSION=[product release version], REV=[OS Major.Minor].[YYYY.MM.DD]

For packages that are not Solaris Release specific (meaning the package is supported on all Solaris Sun Management Center supported releases, the [OS Major.Minor] string must be out of the REV string.


Component Naming

All components must have a unique name to avoid component collision at install time.


Package Dependencies

When installing modules, SUNWesagt is the suggested package dependency. When installing a console bean, SUNWessrv is the suggested package dependency.


Prototype File

The Sun Management Center team uses explicit entries in their packaging to facilitate clarity for developers when maintaining the prototype files.


Sun Management Center Module Name Practices

Sun Management Center modules are installed in a specific directory. So that there are no conflicts with the modules developed by other users, you need to ensure the uniqueness of your module filenames. It is suggested that you use the registry that is setup by Sun Management Center. Please visit the following website for more information:

http://www.sun.com/sunmanagementcenter/


Note - The above discussion is applicable for the console help files also.



Previous Next Contents Generated Index Home

Copyright © 2000 Sun Microsystems, Inc. All Rights Reserved.