This is the Readme file for the Qube 3 sample package file, sample.qube3.pkg. This file provides the components needed for creating a package file for the Qube 3. For more information, see the chapter on "Making Sausalito-Aware Applications" in Sausalito Developer's Guide at http://developer.cobalt.com/devnet/technotes/ sample.qube3.pkg is a tar file. To open it: 1. Create a directory for opening the file, for example: qube3. 2. Type: tar -xzf sample.qube3.pkg After you have opened the file, you see the packing_list file, and these directories: RPMS, pkginfo, and scripts. Note: The # key is a common character. Certain options are determined by the presence or absence of fields in the packing list. To adapt the packing_list file: 1. Use an editor to open the packing_list file. 2. Type the information in the file in the strings that are in this notation: [[string]]; the string in double square brackets ([[) correspond to the msgids in the package.po file, located in the pkginfo directory. 3. Choose whether the PackageType is "update" or "complete." Put that value in the PackageType line. 4. Add each RPM file on its own line. 5. Save the file with your vendor or product name. To add RPM files to the RPMS directory: 1. Change directories to the RPMS directory. 2. Add the RPM files that you want to include in this directory. To change the pkginfo directory: 1. Change directories to the pkginfo directory. 2. Edit the files in there, for example, locale and the file in the "en" directory. All the message IDs found here in the locale files correspond to the strings in double square brackets ([[) in the packing_list file. 3. To change these strings, edit the package locale file. 4. Type the values for the msgstrs as shown below: pkginfo mypackage.po msgid "name" msgstr "My Package Name" msgid "vendor" msgstr "My Vendor Name" msgid "version" msgstr "My Version" msgid "shortDesc" msgstr "This is a sample short description." msgid "longDesc" msgstr "This is a sample long description." msgid "copyright" msgstr "(c) 2000 My Vendor Copyright" msgid "license" msgstr "Do you accept this license? You can format me by specifying HTML tags." 4. To compile the file, type: msgfmt -e "mypackage.po" This causes the file to be a binary file: "mypackage.mo. " To change the scripts: 1. Change directories to the scripts directory. 2. Edit the stub files in the post-install, post-uninstall, pre-install, and pre-uninstall directories. To repackage your package file: 1. Remove the original package file from the directory in which you will tar the package file. 2. Create a new name for the package file. 2. Type: tar czf ../filename.pkg * where filename is the new package name. This creates a filename.pkg one directory above. Please direct feedback to devpubs@cobalt.com