Piecuu/pmaports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

ci: relax pkgrel changes for packages that don’t have remote sources

Browse source 
Motivation is to avoid unnecessary overhead for MR authors & no reason to
actually use pkgrel for meta-packages.

So instead, recommend pkgver-bumps & pkgrel=0 for metapackages, but don't
block MRs when they bumped the "wrong" one. Just make everyone's life easier.

Discussed at <https://docs.postmarketos.org/policies-and-processes/governance/team-meetings/meeting-notes.html> (2026-03-16)

Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8302>
This commit is contained in:
Achill Gilgenast 2026-04-07 22:53:25 +02:00 • committed by The Friendly Meow (merge) Bot
parent 90aeb1d4de
commit e38532b7f7
No known key found for this signature in database
2 changed files with 16 additions and 22 deletions
Download patch file Download diff file Expand all files Collapse all files

10
docs/packaging-guidelines.md
View file

@ -264,3 +264,13 @@ 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`).