mizdebsk added a new comment to an issue you are following:
``
@ngompa Ursa-major won't stop you from using current libsolv-based dependency solvers.
Ursa-major does not make Koji use modules, but module contents, which are just RPMs which
dependencies can be solved with libsolv. No module-specific DNF code would be used in
resolving build dependencies after enabling ursa-major.
Let me explain how ursa-major affects Koji buildroots in more detail.
Current inheritance for ursine build tag f30-build is:
```
f30-build (4380)
└─f30-override (4379)
└─f30-updates (4373)
└─f30 (4368)
```
What ursa-major does is inserting module tags into appropriate place of this tag
inheritance tree. For example:
```
f30-build (4380)
└─f30-override (4379)
├─module-nodejs-10-20180920144631-a5b0195c (4770)
├─module-javapackages-tools-201801-20180806152918-b43b0c8f (4300)
└─f30-updates (4373)
└─f30 (4368)
```
This way contents of selected modules are included in buildroot of non-modular packages.
Modules temselves are not added to buildroots. Module contents take precedence over
contents of f30 and f30-updates, but can still be overriden by buildroot overrides.
f30-build repository generated by Koji from this tag tree does not contain module
metadata. It is still plain-old non-modular YUM repository.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7840