> One thing that concerns me is that now when srpms require certain packages,
> this information is visible from the source repo. I can run repoquery to
> check that nothing requires what I intent to orphan etc. If we generate
> those, we should make sure the srpms we put in the source repo have the info
> in them available.
That's pretty much what I wrote in
https://github.com/rpm-software-management/rpm/issues/104#issuecomment-431577981
if you want to do this kind of thing, you need either to redefine srpms as
"current srpm + result of %buildrequires" or some other format between current
srpms and rpms which is "current srpm + result of %buildrequires" .
And then just output this format during builds, store it in repos the usual
way, query it with repoquery, etc. Since the solution proposed by @ffesti does
not require any special new rpm header, as long as you output this format, I
don't think the rest of the tooling needs any specific adaptation.
But, that's an enhancement. It's not strictly necessary to make dynamic
buildrequires work.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/104#issuecomment-433054259
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
