Leapp Logo

Contents:

  • Building blocks and architecture
  • Installation
  • Tutorials
  • Best Practices for actor development
  • Tests for actors
  • Libraries and API
  • Packaging and dependencies
    • How to deal with dependencies
    • Compatibility between leapp and leapp repositories
    • Naming schema of Leapp-related packages
  • Contributing to the Leapp project
  • Frequently Asked Questions
  • Python documentation for the leapp package
Leapp
  • Packaging and dependencies
  • Naming schema of Leapp-related packages
  • View page source

Naming schema of Leapp-related packages

All projects under OAMG should use the same schema for names of RPM builds, to be able to simply and quickly find specific builds. The schema itself looks like this (NVR without %{dist}):

  • for builds made from the main branch:

<name>-<version>-100.<timestamp>.<short-hash>.<branch>
  • for builds made from pull-request:

<name>-<version>-0.<timestamp>.<short-hash>.<branch>.PR<number>

Where:

  • name is name of the project

  • version is current version of the application

  • timestamp in format: +%Y%m%d%H%MZ, e.g. ā€œ201812211407Zā€

  • short-hash is a shortened hash of the commit from which the build has been created

  • branch is name of the branch from which the builds have been created; in case the name of the branch contains dashes (-), these are automatically replaced by underscore (_) because dash is used as a separator in the name of a (S)RPM file; it is suggested (not required) to avoid dashes in names of branches

  • number is number of a pull-request (alternatively merge-request) to which builds are related

Previous Next

© Copyright 2025, Leapp Team.

Built with Sphinx using a theme provided by Read the Docs.