User story #12164
Add a package provider for zypper patterns
Currently we support the zypper package manager, which uses zypper and rpm to manage packages.
To be able to handle properly the zypper patterns, we need to manage a cache of the list of installed packages.
The metapackages installed when installing a pattern do not have the same name, so the easiest way to implement patterns is:
- to add a new zypper-pattern package provider
- manage the pattern list using zypper instead of rpm
We will want to invalidate cache of the other provider when using zypper of zypper-pattern in the generic method to avoid package list mismatch.
This new provider (package module) will be based on the zypper one with a "-t pattern", plus a new parser for the list of installed patterns through zypper instead of rpm for the zypper module.
It would probably be upstreamable too.
#17 Updated by Félix DALLIDET 5 months ago
I was missing informartion on how zypper is supposed to handle the removal and the update of patterns, luckily re-building patterns is not documented but really easy.
=> it can be done with rpmrebuild on the rpm source pattern file, changing the packages provided is just changing dependencies of the pattern
=> changing version is just changeing a line in the rpm spec file
From now we should be able to build tests with a local repo and patterns in it.