Creating Add-on Products With Add-on Product Creator | Deployment Guide

SUSE Linux Enterprise Desktop Documentation › Deployment Guide › Imaging and Creating Products › Creating Add-on Products With Add-on Product Creator

Applies to SUSE Linux Enterprise Desktop 12

14 Creating Add-on Products With Add-on Product Creator

14.1 Creating Images
14.2 Add-on Structure

An add-on is a special designed media, usually a CD or DVD, to extend SUSE Linux Enterprise Desktop with your product. The Add-on Product Creator was developed to support customers and partners and simplify third-party software distribution for all SUSE products.

To be able to use the Add-on Product Creator you need to install the package yast2-add-on-creator from the SUSE Software Development Kit. The SDK is an add-on product for SUSE Linux Enterprise and is available for download from http://download.suse.com/. Search for SUSE Linux Enterprise Software Development Kit.

14.1 Creating Images #

To create an image of an add-on product, proceed as follows:

Start YaST and open the Add-on Creator module.
If you have not created an add-on before, click Create an Add-on from the Beginning to start. Alternatively, you may create the add-on based on an existing add-on product.Specify the path to the directory containing the data—this may also be a mounted iso image or a CD/DVD.
In case you have already created an add-On, the window shows a list of all existing add-ons. You may Edit or Delete them. Choose Add to create a new one.
This tutorial explains how to Create an Add-on from the Beginning.
Enter the name (Add-on Product Label) and the version of your add-on and provide additional information:
- Under Required Product choose the SUSE Linux product for which to create the add-on.
- Select the path to a directory containing the add-on product packages.
- Optionally, choose the path to a directory containing RPM packages from the Required Product. Typically, these packages originate in the required product (already chosen) and are not part of the add-on itself, but other packages from the add-on depend on them. These packages will not be added to the add-on product, but can be used to create patterns.
Proceed with Next.
Each installation media contains a content file and a product file defining the add-on product. Use this dialog to provide the data for both files. Select an entry and choose Edit to set or change a value. Alternatively, double-click an entry. See Help for more information and possible values.
To import values from an existing content or product file, choose the respective Import button.
You need to at least enter values for Product architectures, Product name and Vendor name of the content file. Proceed with Next.
Enter or change the package descriptions on the next screen. Use Add Language to insert a new language and add translated descriptions (this step is optional). You may also Import existing package descriptions.
Proceed with Next.
Optionally, add patterns in the next step. With patterns you can group your RPM packages. Use New to add a new pattern name and change the respective attributes in the list below. Check Required Pattern for patterns that will automatically be selected for installation when installing the add-on product.
Proceed with Next.
Provide a path to the output directory. If you rather want to create an iso image, check Create ISO Image and provide a file name. Select Create Changelog to create a file containing the changelog entries of all packages included in your product. Additionally, you can modify the workflow and add files:
- Use Configure Workflow to enter files to customize your product workflow. This way you can, for example, insert additional dialogs with options into the add-on installation process that are needed for the correct product operation. See Help for more information.
- Use Optional Files to the following files to your add-on product:
  info.txt
  A text file containing general information about the add-on product.
  License Files
  Add files containing license information in various languages. The files are named license.LANGUAGE, for example license.en_US.
  README Files
  Add README files with a name of your choice.
  Enter the content of the files in the respective text boxes. Alternatively, Import the content from an existing file.
Proceed with Next.
Sign your add-on product with your GPG key to provide evidence of the origin of your product. If you do not have a key, create one first and enter the respective passphrase twice.
Check your settings in the configuration summary and proceed with Finish. Choose the Back buttons to change a setting.

14.2 Add-on Structure #

An add-on product contains the following files and directories:

ARCHIVES.gz: Contains information about all packages included (the output of rpm -qil for each package). This file is compressed with gzip.
Changelog: Contains all the changes of the RPM files ordered by date of change.
content: The content file created during the add-on setup.
content.asc: The GPG signature file.
content.key, gpg-pubkey-NUMBER.asc: The public GPG key.
INDEX.gz: A list of all RPM files. This file is compressed with gzip.
ls-lR.gz: A list of all files and directories of the add-on product medium. This file is compressed with gzip.
media.N/: Contains files with basic information about the add-on media set. The directory is numbered, so media.1/ is for the first add-on medium (for example DVD1). Additional media have a consecutive number.
suse/: Contains sub directories with architecture-specific information. Exceptions are noarch/ for architecture-independent packages, and src/ for source packages. Proprietary software packages are stored under nosrc/.

Print this page