Package maintenance

From Apertis
Jump to: navigation, search

Apertis hosts its own package subset in Collabora's Open Build Service (OBS) instance. These OBS projects are used to host packages which makes up Apertis.

Packages Guidelines

The package set is distributed in several OBS projects: target, development, sdk, hmi, helper-libs. Those projects are merged in a single repository, and split in what distribution names repository components (target, development, sdk, hmi, helper-libs).

  • Source packages in target, development, sdk, hmi, helper-libs must be free/open source software.
  • Source packages in target, hmi or helper-libs cannot be GPLv3 licensed.
  • Source packages in development are either to satisfy build dependencies from target, hmi or helper-libs; or to provide development tools.
  • Source packages modified from upstream distribution include a versioning suffix 'co'.
  • Source packages hosted in Apertis Git must contain an identification file in OBS (i.e. a file name MAINTAINED_IN_GIT.txt)
  • Source packages in SDK are built only for supported SDK architectures (Intel 64 bit)
  • Source packages in target, development, hmi, helper-libs are built for all supported architectures (ARM hard float, ARM 64bit, Intel 64 bit)

Target images contain target and hmi components. Development images include everything target images do plus basic development/debug tools, and thus are allowed to pull packages from development.

Requesting a new package

If a new package is desired, the request should be placed in Apertis issue tracker.

Third party software projects

Third party Git tree projects are meant to help with rebasing Apertis patches against newer upstream versions. Those projects are updated in best effort bases, if you plan to work on them make sure that Git tree is in sync with the package found in OBS. These projects do not contain Apertis packaging directories.

Personal tools