Skip to content
Snippets Groups Projects
Commit dccee1ef authored by Martyn Welch's avatar Martyn Welch
Browse files

Update and move more docs to policies


Update the images and package maintenance pages and move them to polices.

The licensing section on the images pages is out of place. The process for
package management has changed now that we have everything in gitlab. We
no longer need a "MAINTAINED_IN_GIT.txt" file and the "third-party"
repositories have become redundant.

Signed-off-by: default avatarMartyn Welch <martyn.welch@collabora.com>
parent a65ab8be
No related branches found
No related tags found
1 merge request!35Next bunch of website updates
......@@ -39,7 +39,3 @@ Hardware]( {{< ref "/reference_hardware/_index.md" >}} )):
- **armhf**: ARM 32bit (using u-boot)
- **arm64**: ARM 64bit (using u-boot)
The
[licensing](https://designs.apertis.org/latest/license-applying.html)
documentation describes the licensing expectations for the packages
provided in each Apertis image type.
\ No newline at end of file
......@@ -9,14 +9,16 @@ aliases = [
]
+++
Apertis hosts its own package subset in [Collabora's Open Build Service
(OBS) instance](https://build.collabora.co.uk). These OBS projects are
used to host packages which makes up Apertis.
Apertis hosts its own package subset on the
[Apertis GitLab instance](https://gitlab.apertis.org/). On successful
completion of the CI pipeline these are uploaded to
[Collabora's Open Build Service (OBS) instance](https://build.collabora.co.uk)
where the packages are formally built and hosted for Apertis.
## Packages Guidelines
The package set is distributed in several OBS projects: `target`,
`development`, `sdk`, `hmi`, `helper-libs`. Those projects are merged in
The package set is distributed in several groups: `target`,
`development`, `sdk`, `hmi`, `helper-libs`. Those groups are merged in
a single repository, and split in what distribution names repository
components (`target`, `development`, `sdk`, `hmi`, `helper-libs`).
......@@ -27,9 +29,6 @@ documentation for details.
- Source packages modified from upstream distribution include a
versioning suffix 'co'.
- Source packages hosted in [Apertis Git](https://gitlab.apertis.org)
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
......@@ -41,14 +40,5 @@ images can refer to `development` components.
## Requesting a new package
If a new package is desired, the request should be placed in [Apertis
issue tracker](https://phabricator.apertis.org).
## Third party software projects
[Third party Git](https://gitlab.apertis.org/third-party) 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.
\ No newline at end of file
If a new package is desired, the request should be made following the relevant
[process](https://designs.apertis.org/latest/contribution-process.html#extending-apertis).
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment