Hi folks,
I found this thing and thought it might be useful for testing depended
packages before committing, something similar to the chain scratch
builds in koji, that are not available (to my knowledge).
I didn't realize before we can use module builds for any package set,
that does not even relate to any existing module in Fedora, so sharing
for anybody who finds this useful.
The use case here is that we have two or more packages that we want to
test before changes land in production branch in dist-git, and where
copr is not enough (for example we want all koji arches). (yes, for many
things copr is much more powerful tool)
The idea is to run a modular scratch build that picks the packages from
concrete dist-git branches and build them in an expected order.
The changes must be in a branch in dist-git (not in a fork), but it can
be a private branch. Then we need a modulemd file like this:
$ cat > testmodule.yaml <<EOF
---
document: modulemd
version: 2
data:
name: testmodule
stream: 1.0
summary: Testing a thing
description: Just for a testing purposes
license:
module: [MIT]
dependencies:
- buildrequires:
platform: [f34]
requires:
platform: [f34]
components:
rpms:
autoconf:
rationale: autoconf-2.71
ref: cb2040cb # this can be a specific hash or a branch name
buildorder: 0
dovecot:
rationale: package to be tested
ref: f34
buildorder: 1
EOF
$ fedpkg module-build --scratch --file testmodule.yaml --watch
Enjoy ;)
Honza
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
