Article 26946 of comp.unix.solaris:
Path: mri-gw!psinntp!psinntp!psinntp!gatech!news.sprintlink.net!demon!paramedx.demon.co.uk!Adam
From: Adam Lovick <Adam@paramedx.demon.co.uk>
Newsgroups: comp.unix.solaris
Subject: Re: pkgadd white paper ?
Date: 24 May 1995 23:14:16 +0100
Organization: home
Lines: 55
Sender: news@news.demon.co.uk
Message-ID: <801352080snz@paramedx.demon.co.uk>
References: <3pslc6$48n@imp.demon.co.uk>
Reply-To: adam@paramedx.demon.co.uk
NNTP-Posting-Host: dispatch.demon.co.uk
X-Newsreader: Demon Internet Simple News v1.29
X-Posting-Host: paramedx.demon.co.uk

In article <3pslc6$48n@imp.demon.co.uk> bs1@$DOMAIN "Bern Spence" writes:
> 
> I`ve been presented with the problem of converting our application
> into a format that will allow installation using the pkgadd(1)
> command.
> 
> ...snip...
> 
> Has anyone seen a white paper on the subject or have any information
> that would be helpful?
> 
> Also, is there a set naming convention for packages, Sun seem to
> prefix their packages with SUNW (what is the significance of the W?).
> 
> Thanks
> Bern
> 

First get all your bits and pieces together in a hierarchy, similar to
what you want on your targets. Then run the commands, pretty much like
this:

vi yourself a copyright file

pkgproto > prototype
   to create a prototype file. You might well need to edit this to add
   things like your copyright file and any other 'information' files.

pkgmk
   By default this places the package into /var/spool/pkg and is a
   decent place to start checking it. You can run pkgadds from here
   (followed by pkgrms and so on) to test it.

You might want to create a pre or post install script, which caters for
special things a straight copy won't do properly (eg symbolic links) and
a pre and post remove script to do the same for backing out.

Once you're happy, either do a pkgmk -d /dev/rmt/0 or do pkgtrans to
transfer the package image from /var/spool/pkg onto your tape. The
acid test; delete /var/spool/pkg/THING, and run your pkgadd -d /dev/rmt/0
and cross your fingers.

As to a naming convention, stick to something that identifies you:
BERNutils, BERNgui and so on.

It makes recovering from disasters easy and taking benchmarks to outside
companies are a breeze. Tape in; pkgadd; run the tests and get the results;
pkgrm, and away you go.

All the best.


-- 
Adam Lovick
adam@paramedx.demon.co.uk


Article 27075 of comp.unix.solaris:
Path: mri-gw!psinntp!psinntp!psinntp!gatech!gt-news!cc.gatech.edu!news.cc.gatech.edu!rdk
From: rdk@fauna.cc.gatech.edu (Bobby Krupczak)
Newsgroups: comp.unix.solaris
Subject: Re: pkgadd white paper ?
Date: 26 May 1995 13:55:37 GMT
Organization: College of Computing
Lines: 17
Distribution: inet
Message-ID: <RDK.95May26095538@fauna.cc.gatech.edu>
References: <3pslc6$48n@imp.demon.co.uk> <3q2qin$ol1@koppel.East.Sun.COM>
NNTP-Posting-Host: fauna.cc.gatech.edu
NNTP-Posting-User: rdk
In-reply-to: Richard.Elling@East.Sun.Com's message of 25 May 1995 20:50:31 GMT


>   Good move!  You will like packages!

I like them as well!

>   Hmmm... you should find the _Developer's Guide to Application Packaging_
>   on the Solaris Software Developer's Answerbook.  You may also find SVR4
>   books which talk about how to make and manage packages.

I thought it was somewhat lacking.  Below is a URL for a "white-paper"
on package creation.  It walks you through a real simple package
creation.  I can send you example scripts and stuff I use to create a
package as well.

Bobby

ftp://sunsite.unc.edu/pub/sun-info/white-papers/packaging-for-solaris2.ps