> Maybe I'm missing the point of the issue (OP to decide), but I think this has
> real and pretty trivial engineering solution for some languages: -
> distribution provides heuristic for language Foo in foo-build package -
> package Baz puts 'foo-build' into build requires - package Baz adds
> "%build_requires --script %foo_analyzer" to declare that the buildsystem
> should attempt to generate build requires after %prep with %foo_analyzer
> script - this brings new file/value in generated SRPM to let build-system
> know - mock finds %build_requires section in SRPM, so it - does installroot +
> and installs BuildRequires as usually - runs %prep - runs %foo_analyzer from
> %build_requires - runs the rest of the build
That would work too, as long as you take into account a package may declare
several %foo_analyzer s and you probably need to loop their execution with BR
population till there is no new results to handle complex cases transparently.
That's an analog of my "implicit looping".
Replace script with --command to make the people that reimplement everything as
binaries happy
--
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-366427605
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
