[modularity] Querying modular content — workaround

[Adam Samalik <asamalik@xxxxxxxxxx>]

I've just published a blog post about querying modular content [1] which might be useful if you maintain modules.

It should help you, at least partly, in the following example scenarios:

Rebuilding dependencies after major changes
* A new version of an interpreted language lands in Fedora as a set of standalone packages. All packages depending on that language — both standalone and modular — need to be rebuilt.
* An ABI change is brought by a new package version and all of its dependencies — both standalone and modular — need to be rebuilt.

Retiring packages
* A packager decides to retire a library. They check whether any other packages — both standalone and modular — require it before they can retire it.

Discovering content with a CVE
* A CVE has been found in Django 1.6. The security team needs to find out whether we ship Django 1.6 in Fedora either as a standalone or a modular package.

[1] https://blog.samalik.com/2019/01/14/querying-modular-content.html
--

Adam Šamalík
---------------------------

Software Engineer
Red Hat

_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx