Section 1-Package The following questions are used to describe your package, the file which delivers your product. Package Type By specifying the type of package being built, the packager can better detect invalid files within your base directory, and warn you of any problems. What type of package is this? (options: Application,Library,Development,Documentation,Source code,Other) Release Number A package release number is used to show that you are re-releasing a package. It is independent of the version of your product. For example, if you accidentally forgot a few files in this package, you would repackage your product with the new files and increase the package release number. What is the package release number? (release number autoincrements if build number stays the same) Release Notes Since you are repackaging this product, you have the opportunity to explain why a user should upgrade to this new package. This information appears to a user when they are using an auto updating utility. What are your package release notes? (full multi-line description) Release Urgency Since you are repackaging this product, users will want to know the priority of this re-release. Package updating utilities may use this priority to decide if the user should be automatically notified of your re-release. A low priority release will not alert the user; this includes would changes to descriptions, web pages, and other non critical Package Manifest changes. A medium priority release may alert the user with the package release note and let the user decide if they should reinstall the package; minor bugs such missing support files or corrupted A high priority package release means that the user should immediately update to this package; packages released with dangerous or unrecoverable errors (such as a virus or corrupt files) should be released with a high urgency. What is your release priority: Low/Medium/High? (options: Low,Medium,High) Repository URL If you administer your own package repository site or know the URL to the repository which is housing your software, you can store this in your package description. If the file which describes your package (*.qpm) becomes separated from the package itself (*.qpk), the package installer may still be able to find your package by going to the repository where your package is distributed. What is the distribution repository URL? Section 2-Product The following questions are used to describe your product. Your product is the contents of the package you are building. Product Name Each product has a name which is displayed during installation and maintenance. Your product name may be any number of letters and characters, but should not have a version number included in the string. What is the full name of your product? Product Identifier Each product has a unique identifier--a word or set of characters without whitespace. Other developers can use this product identifier to build dependencies with your product. In the future, if you release a new version of your product, but break compatibility in some way, you should change your product identifier. Your product identifier also helps to ensure that your software will not be installed over anyone else's software. What is your product identifier? Email contacts By entering email contact information, your package will include references to direct users to the product, vendor, and author's email addresses. Enter (Y) if you have any of this information available. Will this package include any email contact information [Y/N] ? (options: Yes,No) Product Email If you have an email for feedback about your product, various package utilities can extract this and make it available to users. What is the product's email address? Vendor Name Because you are building this product's package, you represent the maintainer, vendor or distributor of this product. Your name, the name of your company or the organization you represent should be available to the user. This name can differ from the software author. If you are porting publicly available source code, please enter Public as the vendor name. What is your full vendor name? Vendor Identifier Each vendor has a unique identifier, a word or set of characters without whitespace. Other developers can use this identifier to distinguish your distribution of a particular product. Your vendor identifier also helps to ensure that your software will not be installed over anyone else's software. If you are porting publicly available source code, please enter public as the vendor install name name. What is your vendor identifier? Vendor Home Page If you, your company or organization has a web site, graphical package installers can redirect users to your web site for more information about the product you distribute. What is the vendor web page URL? Embedded Web Pages By entering embedded web pages in your package, package installers can show immediate well-formed information or links regarding your product as the operator is deciding whether to install your package. If no embedded web pages are entered for either the product, vendor, or author, then the textual description information will be used. Will this package include any embedded web pages [Y/N] ? (options: Yes,No) Vendor Embedded Home Page The QNX Package Installer allows you to embed web pages along the right side of the repository window. When a user selects your package, they have the opportunity to see more information about you, your company or organization. This embedded web page is 290 pixels wide and may be resized as tall as necessary. What is the embedded vendor web page URL? Vendor Email If you have an email for questions about you, your company or organization, various package utilities can extract this and make it available to users. Your organization's email address? Author Name The name of the person, company or organization who authored this product may be different from the vendor or distributor of the package. What is name of the author? Author Home Page If the author, company or organization has a web site, graphical package installers can redirect users to the web site for more information about the product they have written. What is the author's web page URL? Author Embedded Home Page The QNX Package Installer allows you to embed web pages along the right side of the repository window. When a user selects your package, they have the opportunity to see more information about the author of this product. This embedded web page is 290 pixels wide and may be resized as tall as necessary. What is the embedded author web page URL? Author Email If you have an email address allowing questions for the author, various package utilities can extract this and make it available to users. What is the author's email address? Small Product Icon By specifying a small icon for this product, the package installer can display your specific icon (rather than the default category icon) with information about your package. If you enter a local file (/filename), the file will be copied into the repositiory. What is the URL for this package's small icon? Large Product Icon By specifying a large icon for this product, the package installer can display your specific icon (rather than the default category icon) with information about your package. If you enter a local file (/filename), the file will be copied into the repositiory. What is the URL for this package's large icon? Short Description A short description of a product should be a single sentence describing the product, about sixty characters in length. Package utilities will use the short description as a one-line summary of the product. What is the short description of this product? Full Description A long description of the product is a text summary of the features of this version of the product. In the QNX Package Installer, the long text description is shown if an embedded web page is unavailable for the product. What is the long description of this product? (full multi-line description) Product Home Page If your product has a web site, graphical package installers can redirect users to your web site for more information about your product. What is the product's web page URL? Product Embedded Home Page The QNX Package Installer allows you to embed web pages along the right side of the repository window. When a user selects your package, they have the opportunity to see a page describing this product. This embedded web page is 290 pixels wide and may be resized as tall as necessary. What is the embedded product's web page URL? Section 3-Release The following questions relate to this particular release, the version of the software you bundling into a package. Release Date You can release your software whenever you want; it can be unrelated to the date that this package is created. The QNX Package Installer will not show software in a repository before its release date (format: YYYY/MM/DD). What is the release date for this product? (inserts today's date by default) Version Number The version of this product is a string useable by other package builders to build dependencies. If you make changes to your software you may either re-release the package (change the release number), change this version number or change the build number (for internal releases). These three numbers ensure that your software distribution will not collide with older builds of your product. What is the version of this product? Version Urgency If this product had been previously released, users will want to know the priority of this new version. Package updating utilities may use this priority to decide if the user should be automatically notified of your product. A low priority product release will not alert the user. These types of version changes may include minor bug fixes or aesthetic changes. A medium priority product release may alert the user with the minor release notes for this version. A medium priority release is a recommended update with potentially new features, bug fixes or documentation changes. A high priority product release represents a substantial upgrade from previous versions of the product. Users may be alerted with major and minor release notes if they are deciding to install or upgrade to this product. What is your version release priority: Low/Medium/High? (options: Low,Medium,High) Release Stability Packages may be full distributions or patches to previous distributions and will be identified as containing Experimental, Beta, or Stable software. Experimental software is released for trial purposes only. It's intended to test or verify bug fixes or to provide a glimpse of what might be in store for the future. Beta software is more stable yet may contain bugs and instability or may change drastically in the next release. Stable software is considered to be highly stable code. What level of stability is this release? (options: Stable,Experimental,Beta) Minor Release Note When a new version of the product is released, some users may upgrade to this version, while others may be installing for the first time. An auto-updater utility may display the minor release notes to let user know what features are added to this new version. Many products represent their versions with a major and minor number, i.e.. 2.1. If you are moving from 2.1 to 3.0, a major release note is important. If the user is moving from 2.1 to 2.2, the major release note is not important - only the minor release notes. What are the minor release notes for this version? Major Release Note When a new version of the product is released, some users may upgrade to this version, while others may be installing for the first time. An auto-updater utility may display the major release note to let user know what features are added to this version. Many products represent their versions with a major and minor number, i.e.. 2.1. If you are moving from 2.1 to 3.0, a major release note is important. If the user is moving from 2.1 to 2.2, the major release note is not important - only the minor release notes. What are the major release notes for this version? (full multi-line description) Build Number While in development, you may wish to produce newer versions of this product. A build number enables you to differentiate from one version to the next, without adjusting the actual version number of the product. When you release your product (and increment the version) is it recommended that you reset your build number back to 1. What is your current build number? (sets release number to 1 if this number changes) Excluded Countries Some countries have restrictions on a variety of software - from games to encryption algorithms. The QNX Package Installer attempts to honor these trade regulations by recognizing countries where a product is restricted. Countries are represented by their two letter country code, these standard country codes are available online. Search for 'ISO-3166-1 Country Names' to find numerous online references. Separate multiple countries with a comma-delimited list. What 2-letter countries are to be excluded? License Type Much of today's software is released with licenses and includes copyright or usage restrictions. You may choose to define which license or type of license this product is bound to. What type of license applies? (options: No License,Custom License,Public Domain License,QNX Open Community License,QNX Community License,QNX Confidential Source License,Artistic License,Apache Software License,BSD License,Demo License,GNU General Public License,GNU Lesser General Public License,IBM Public License,Intel Open Source License,MIT License,Mozilla Public License,Python License,QT Public License,Sun Internet Standards Source License,zlib/libpng License) License URL By specifying the location of the license text, you ensure that anyone installing your package will be forced to view the license you have specified. To enter custom text which is on your hard drive, enter the explicit path to the document, starting with a '/'. Packager will copy the file from your local hard disk into the repository and will automatically reference it using the (rep://) notation, which points to the repository itself. To specify a license file external to the repository, enter the URL to the license text (http://). If you are only creating a QPK/QPM pair, you probably want to reference their repository using (rep://license.txt) or some other license file which is expected to be in the final repository. What is the package license URL? Section 4-Content The following questions are used to describe the contents of your product. Topic Your product must be categorized into one or more of the following predefined topics, to help consistently organize software within a repository. What topic best describes this product? (select a topic from the available hierarchy) Content Keywords By entering keywords related to your product, a fast search can be performed by users looking for software which meets their needs explicitly. Any number of keywords may be entered, but adding too many will reduce the effectiveness of using keywords at all. Separate each keyword by a comma and enter no spaces. Enter comma-delimited keywords: Display Environment The QNX operating system supports a number of display environments including the Photon microGUI, X11R6, and text mode. Not all software requires a display: background or daemon processes may not have any requirements for user interaction. What display requirements does your software have? (options: X11R6,Photon,Console,Full-screen console,None) Target Audience Most software is written for a particular type of audience: developers, users, or perhaps system administrators. By defining your audience, package installers can filter a repository, to show only the software in which a particular operator is interested. Who is your software targetting? (options: Developer,Administrator,User,Other) Product Requirements If this package requires any other packages or libaries in order to execute correctly, you may enter a textual description of such requirements below. The actual dependency commands will be described later (after the packages have been sorted). For example: This package requires the GTK libraries to operate correctly. Enter comments regarding any libraries or packages required. (full multi-line description)