I am not at all against having scripts for normal dependency generation. But 
their are a few important differences to the BuildRequires:

- They have to be attached to a sub package and cannot be global
- We may want to (be able to) associate the script to files - so we need a way 
of passing the fileattr macros (path, flags, magic).
- They don't need the funky stop build, install new deps and restart build cycle
So they need to be done a different way as the %generate_buildrequires script 
anyway. So while I agree we should add those it is probably best to concentrate 
on the topic at hand first.

Also not sure if %generate_buildrequires vs %generate buildrequires really 
makes a lot of difference.


-- 
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/pull/593#issuecomment-437367098
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint

Reply via email to