> I can run repoquery to check that nothing requires what I intent to retire
> etc. If we generate those, we should make sure the srpms we put in the source
> repo have the info in them available.
I can imagine `rpmbuild -bs --try-really-hard` which would:
1) generate src.rpm the classic way
2) run %prep and %buildrequires
3) generate new src.rpm with injected requires from %buildrequires
I can make support in mock for that and we can make this default in Koji, so
all builds from Koji will have full set of buildrequires and you can still
repoquery them.
I am not afraid about Koji/Mock, but what about OBS @mlschroe ?
--
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-433249318
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
