[Rpm-maint] [rpm-software-management/rpm] RFE: support package-level dependency generators (Issue #2392)

[Panu Matilainen]

The "internal" dependency generator is built around file-specific dependencies. While many types of dependencies indeed are specific to a single file (eg ELF), this is not the always the case. For example, Python egg-info may be a single file or a directory worth of metadata, but in neither case is the data critical to running the software, the metadata is about the entire Python-level "package" which often is not meaningfully splittable to further sub-components. In which case, per-file dependencies do not make much sense. 

We should have a generator flag that passes all matching files in the package to the generator at once and collect the dependencies on package, rather than file-level. This allows the generator (script) to reason about dependencies split over multiple files and cover cases where file-level dependencies do not make sense. This is like a cross between the current internal and external generators, the main difference to the external generator being that the applicable file matching is still done on rpm-side instead of the generator (script).

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2392
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/issues/2392 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20230213/84825587/attachment.html>