Le vendredi 21 juin 2019 à 18:32 -0500, Jason L Tibbitts III a écrit : > > > > > > "MC" == Michael Cronenworth <mike@xxxxxxxxxx> writes: > > I'm disappointed that the macro doesn't emit the > %generate_buildrequires > line as well; I'm not real sure, this would work, for projects that contain stuff involving multiple generators (composing multiple thing is one of the key rpm does well and other tech not so much). That would require rpm to merge all the %generate_buildrequires sections transparently. And that would open the door for packagers to interleave %generate_buildrequires with other things, wich is unlikely to end well. The explicit %generate_buildrequires forces packagers to think how this is all sequenced (especially with %prep and %build commands). The point in the spec where %generate_buildrequires is executed is not as self- evident as one may think. It took at least a year of discussion upstream for everyone to agree the design was correct. -- Nicolas Mailhot _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
