make-3.77-USRPKG.tar.gz (PackageAdd format - installs to /usr/local/make-3.77).
make-3.77-OPTPKG.tar.gz (PackageAdd format - installs to /opt/make-3.77).
make-3.77-SOURCE.tar.gz (Source Code).

	Installation Step	Location	Usage	Accum Usage	Optional Steps to Minimize Usage
	Download pgkname-USRPKG.tar.gz	/pgktmp	0.32 MB	0.32 MB	N/A
	gunzip pgkname-USRPKG.tar.gz	/pgktmp	1.06 MB	1.06 MB	N/A
	tar -xof pkgname-USRPKG.tar	/pgktmp	1.04 MB	2.10 MB	Delete ".tar" file after untarring
	pkgadd -d /pkgtmp pkgname	/usr/local/	1.04 MB	3.14 MB	Delete /pgktmp/pkgname/ after pkgadd

This package installs as decribed in our General Installation Notes. The final pkgadd instruction to install the package is:

"pkgadd -d /pkgtmp make"

The default action, when make was originally compiled was to set the group ID bit on the executable, make. We have chosen to leave this, believing that the GNU folks had good reason to do this (which you may or not agree with).

This being the case, be aware that during the pkgadd process, you will be prompted to confirm whether or not you wish to set the group ID bit on on the executable, make. Generally, we would say that it is probably best to say no, however, you may have an arguably valid reason for wanting to set the group ID bit.

If you installed to /usr/local/, the man pages for this package are located in:

"/usr/local/make-3.77/man/man1"

Adding "/usr/local/make-3.77/man/" to your MANPATH should be sufficient to access all accompanying man pages. However, be aware that since SolarisX86 already shipped with a version of make, and since the man pages for that version are already in your system's MANPATH, be certain to place "/usr/local/make-3.77/man/" in FRONT of your current MANPATH specification so that it will find the man pages for your new version of make before it finds the man pages for your older version of make.

We have created Administrative Notes to assist our site administrators in verifying/reproducing our packaging process. However we have included them as part of our public documentation for two reasons:

1. To allow you the opportunity to verify that the steps we have taken in our packaging process will (or will not) satisfy your specific application needs.
   
   
2. That those of you who are new to the compiling game, may benefit from the information to help you to better understand the compilation process.