Defining new packages

EPMs and FPMs are added as objects to an existing workspace.

Rules for naming packages

• Allowed characters are a-z, A-Z, 0-9, _
  We recommend that you avoid uppercase letters.
• Package names must be unique. A package name may only exist once, regardless of whether it is an EPM or FPM.
  Note, that a unique package name is also relevant for provides, conflicts and requires.
• Package names are composed of the following elements:
  <name>-<version>-<release>.<container>.[epm|fpm]
  Example: baseosrp-6.2302.0-3.UC_RP6_X64.epm
• Do not rename package files after the build process.

Rules for naming udev rules

• udev rules are stored in files with extension .rules
  

• To avoid conflicts, file names for udev rules must be unique. We recommend that you use the corresponding package name in the file name.

• To control the order of processing, start the file name with a two-digit number, maximum 98.
  The rule files are processed in alphanumeric order (higher numbers later than lower ones).

Example of the structure of a file name:
<number>-<origin>-<package name>.rules
A udev rules file from Unicon is for example 91-unicon-keyboard.rules

For further information on udev rules, see https://linux.die.net/man/7/udev.