How to use the epkg tool

epkg combines several functions to build and manage eLux packages. Each function is covered by a specific module.
Example:

• To build an EPM/FPM package, you need to use the Build module. Example:

  epkg Build --container=rp6_x64

Options for creating a build

• To initiate an option, use two minus signs:

  epkg Build --<option>

  Option	Description
  container	Type of target container the package is built for (major eLux version) Allowed values: rp6, rp6_x64, elux7
  skipCheck	Skip building md5 checksums
  skipCreateTree	Skip creating the package tree
  skipCreateEpm	Skip creating EPMs and FPMs
  skipSign	Skip signing the package
  autoIncrementVersion	Automatically increase the release version of changed EPMs and FPMs
  releaseType	Release type of the build (test or release), see below
  testVersion	Version name/number used for test builds Erlaubte Werte: '[a-z]+(+[0-9]+])?'
  debug	Enable debug mode

Help and other commands

epkg --help	General help page across all modules
epkg <ModuleName> --help	Help page of a specific module Allowed values: Build, Convert, ConvertFrom, Install, Upload, New, NewFrom, Info, Sign, UpdateCopyrightInfo
epkg --<ModuleName>	epkg module to be executed Allowed values: Build, Convert, ConvertFrom, Install, Upload, New, NewFrom, Info, Sign, UpdateCopyrightInfo
epkg --log	Enable logging

Test versus Release builds

With epkg, you can build either release packages or test packages. The type of build is controlled by the parameter --releaseType.

epkg ---releaseType=test	Test build (default)
epkg ---releaseType=release	Release build

A test build assigns the label defined by testVersion in the package name. To the package name keeps the underlying release number to which the string defined by testVersion is appended, by default testing.1 from eLux SDK VM 3.12 Earlier versions replaced the existing release number with the string 9999 by default.

Test builds also differ from release builds in the following:

• Some steps such as updating the md5 check sums are skipped.

• Packages created by test builds can be overwritten by the installation in the container.

For examples, see Examples of use.