"@(#)packaging.txt	1.3	94/01/06 SMI"

#
# Copyright 1994 Sun Microsystems, Inc.  All rights reserved.
# Use is subject to license terms.
#


	A Simple Guide to Updating OS-Net Package Definitions


1. WHAT do I need to do?

	Add to and delete entries from these files
		usr/src/pkgdefs/SUNW*/prototype_com
		usr/src/pkgdefs/SUNW*/prototype_i386
		usr/src/pkgdefs/SUNW*/prototype_sparc

2. WHERE do I get the information?

	Mailed output of protocmp done by the nightly build script, for
	each architecture (sparc, i386).

	Or from twice running protocmp yourself, comparing the reference
	(train) proto_list and your_gate proto_list, and comparing your
	usr/src/pkgdefs with your_gate proto_list.  (twice per architecture)

	Also check renames, creates in output from putback -n.

3. HOW can I verify that my updates are correct?

	Another protocmp of usr/src/pkgdefs and your_gate proto_list.

	NOTES:
	   Noise from this comparison is filtered out with an exceptions list
	   (per architecture) in the usr/src/pkgdefs/etc directory.  The
	   nightly script does this for you; if you run protocmp yourself,
	   use the -e option to specify the exceptions list.

4. There are LOTS of packages.
   HOW do I figure out what goes into which package?

	Most frequently you'll update these packages
		SUNWhea		headers
		SUWNcar.* 	kernel arch specific
		SUNWcsr		core Solaris root -- generic stuff in "/"
		SUNWcsu		core Solaris usr  -- generic stuff in "/usr"

	NOTE:
    	Package contents are generally installed in either "/" or "/usr"
	Some packages are installed in "/usr/kvm" and "/opt"
	A package can install into ONLY ONE such partition.

	Check usr/src/pkgdefs/SUNW*/pkginfo.tmpl for information about
	package contents
		fgrep NAME SUNW*/pkginfo.tmpl  (for package names)
		fgrep DESC SUNW*/pkginfo.tmpl  (for package descriptions)

	Get package impact information from developers before letting them
	putback into your gate.  Encourage them to do the updates to package
	definitions.

5.  CAN I build packages?

	run nightly with the -p option
	/opt/ongk/bin/pm is the script that actually builds packages
	(more on this when packages are actually installable)

6.  WHAT are some other things I should be aware of?

	Install Scripts -- scripts included in packages which are run before
	or after a package is installed or removed.

	Class Action Scripts -- used by upgrade to preserve edits to files.
	For more information, see /shared/ON/release_docs/cas/info.

	Adding, renaming, splitting, or deleting a package is a big deal.
	All these operations have impacts on installation clusters.  Also,
	new package names must be registered with Release Engineering to
	ensure they are unique within Sun software products.

7.  Where can I find some generic Solaris packaging documentation?

        SunOS 5.2 Application Packaging and Installation Guide:
	part number 801-3933-10, Rev A.

8.  WHOM do I call for help?

	Specifically, the integration person assigned to your release,
	more generally, the integration group.