On Friday, July 3, 2020 9:51:20 AM CEST Nicolas Mailhot via devel wrote:
it will certainly be possible to compute a second level of sources
during the dynamic buildrequires first pass over prep, and the change
makes the forge macro code modular enough the second level will be
auto-registered in sourcelist, but how is the buildsystem supposed to
provide sources that did not exist during its first pass over the spec
file?
Possible. But I personally think that "dynamic buidlrequires" should stay
working with BuildRequires, not Sources.
and Fabio’s most excellent rewrite of the spectool code (if you have
not used it yet, try it, it’s good). However someone needs to add
lookaside or buildsys integration to spectool to spectool so spectool
has something to source new sources from in a restricted build context.
Let me just state my opinion that I don't like this situation coming.
Packaging should be simple task, and should be made simpler, obvious.
That said, I like that package build is just:
SPEC + sources + patches + build dependencies
I'd appreciate the link to spectool rewrite, though.
Pavel