Ryan, It is pretty easy to create a patch package that patchadd/patchrm will install. You can reverse engineer this from taking a current patch for Solaris off of the SunSolve website. The patch will have the necessary install class scripts that can be copied into the sparse patch packages. Once you have these, and the replacement binaries/files you create for the patch, you can use the pkgmk command to assemble the patch packages.
I built many a patch this way for Cray Research's version of Solaris and other software products. If you have more specific questions, shoot me some email. Bruce Hill Ryan Holliday wrote: >We currently have an in house installation application that bundles and >distributes our software applications to all of our enterprise servers at >multiple sites. We would like to move away from that in house solution and >start bundling and distributing our software using the Solaris Package format. > >The problem is I?m having a hard time figuring out how to patch the packages >after they have been installed. The Application Packaging Developers Guide >recommends creating a sparse package to replace the effected files, which I >assume would be installed using the ?pkgadd? function. > >While that can work, I would really like to use the ?patchadd? functionality >as it would allow us to be more consistent with OS patches and we can use >reuse many of the same tools and code to update our systems. However, I can?t >seem to find much information on how to create a patch in the ?patchadd? >formant. I was hoping someone could point me in the right direction, or even a >how to guide. > >Thanks in advance for any help! > > >This message posted from opensolaris.org >_______________________________________________ >install-discuss mailing list >install-discuss at opensolaris.org >http://opensolaris.org/mailman/listinfo/install-discuss > >
