docs: place the provides section of the packaging guidelines at the end

It is quite massive, and therefore let's put the simpler things
first. If things keep growing, at some point it would make sense to
move it out to a subpage.

Signed-off-by: Pablo Correa Gómez <pabloyoyoista@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8508>
This commit is contained in:
Pablo Correa Gómez 2026-05-08 15:28:02 +02:00 committed by The Friendly Meow (merge) Bot
parent a90be8cc48
commit b293a8e354
No known key found for this signature in database

View file

@ -1,5 +1,15 @@
# Packaging Guidelines
## Meta packages
### Package versioning (pkgver, pkgrel)
Packages without upstream sources are a bit special. These are `device-*`
packages and other packages like `main/postmarketos-base`, where the source
files are included in the package directory. For these packages, the `pkgver`
should always be incremented instead of the `pkgrel` (so that `pkgrel` always
is `0`).
## Provides, priorities, alternatives, and forking packages
The APK concepts around selecting conflicting packages for a same purpose, e.g:
@ -264,13 +274,3 @@ only in some specific circumstances? In those situations we have to:
versioned provider to disambiguate (e.g:
`provides="audio-conf=$pkgver-r$pkgrel"`), or to force the forked packages
to provide a lower version than the other package.
## Meta packages
### Package versioning (pkgver, pkgrel)
Packages without upstream sources are a bit special. These are `device-*`
packages and other packages like `main/postmarketos-base`, where the source
files are included in the package directory. For these packages, the `pkgver`
should always be incremented instead of the `pkgrel` (so that `pkgrel` always
is `0`).