Ideally, you will
The overriding guideline, is to provide a transparent user experience. The user should in all cases be able to do
pkg-get install xyzand have xyz just work, with no extra fuss.
Exceptions to this rule are only if the software needs fundamental by-hand
configuration to do anything useful.
Example: Sun's own packaging of mysql, SFWmysql
Builds will be configured with whatever is equivalent to
All programs and libraries should be built with
export LD_OPTIONS=-R/opt/sfw/libplus any other needed -R type dependancies. They should ONLY be linked against Solaris/Sun provided libraries, and libraries packaged under /opt/sfw
PKG=COMxxxx NAME=long name (or "ShortName - Long name after dash") CATEGORY=("application" or "system") VERSION=x.y.z VENDOR=url://where.you.got.source EMAILemail@example.com DESC=COMmunity build: pkgname x.y.z, pacakged by Your Name
P SFWgtk GTK - The GIMP Toolkit P SFWglib GLIB - Library of useful routines for C programmingIf any packages in the depend file do not begin with "SFW", "SUNW", or "COM", go and read the "Build standards" section of this document.
EVERY SINGLE DYNAMICALLY LINKED LIBRARY used by your package, must have an appropriate entry in your depend file.
# touch /tmp/timestamp [make install, or whatever you do to install the program under /opt/sfw] # find /opt/sfw -newer /tmp/timestamp |pkgproto >prototype.files # (echo "i pkginfo"; echo "i depend" ; cat prototype.files) >prototype # pkgmk -r / -a `uname -p` # pkgtrans -s /var/spool/pkg /tmp/COMyourpkg-`uname -p`.pkg COMyourpkg [ you might also want to do "rm -r /var/spool/pkg/COMyourpkg" now]
You should now have a shiney new package file to submit. Ideally, you will build both a Solaris 8 x86, and a Solaris 8 sparc version.
It is suggested that you keep around your pkginfo and depend files, and any build notes you may have, so that when it comes time to upgrade the package, you have an easier time of it.
If you are not willing to be the ongoing package maintainer for a package, do not submit one in the first place!
Note: We may not accept all packages for inclusion into the archive. Trivial stuff like "this is my favourite screensaver" will most likely NOT be accepted.
Thus, you should probably email Phil before you start making packages.