In general without seeing the diff this is an unanswerable question. In general the larger a pull request to more work and time it will take to get approved. This is a non-linear effort so in the interest of expediency it’s likely worth breaking it up into several small chunks.
However I would actually recommend submitting it as a larger draft PR to be able to get high level feedback on the change before taking the time and effort to break it into smaller chunks. This will give a chance to make sure that it’s overall structurally good, and can make sure things are consistent before getting into the individual details.
That would be great to converge with the rpm generator that’s integrated into bloom.
Scott recently announced that we’re generating RHEL RPM metadata
This work should be extendable to SuSE builds as well. If you’re building in bulk from the rosdistro for a alternative platform a tool that’s already used for Gentoo and Open Embedded is Superflore:
A new entry point could be added and this could be extended to generate rpm’s and upload to OBS leveraging the same core elements.
In the long term we’d like to not duplicate the generators between bloom and superflore and this might be an optimal opportunity to demonstrate integrating the already tested bloom generators into the superflore bulk operations processing of the rosdistro.