On 5/25/21 8:01 AM, Miro Hrončok wrote:
The culprit of trying to maintain them in one component is that they are released independently. Maintaining various subpackages with different versions and release cycles from the same spec file is a huge PITA.However, so is maintaining 100 packages. There is no clear win. I'd personally rather maintain the 100 packages with automatically generated build dependencies, but I would not say it is a *should*.
Thanks for helping me analyze those options.
Have a look at https://src.fedoraproject.org/rpms/pyproject-rpm-macros
Where has this been all my life? 😱
2) Should I 'vendor' the SDK components into a single package and set it as a dependency of the core CLI tools?I'd say doing that is pretty much the same amount of work as maintaining a single-spec multi-package beast mentioned above, but less user friendly.
I was thinking the same. Thanks for confirming it.
3) Should I dynamically generate spec files for the SDK components based on the requirements from the main CLI tools?The spec files should be almost identical with just the name/summary/description/version changing, so I'd say this is a way to go.
👍🏻
4) Am I making this much, much more difficult than it really is? 🤦🏻♂️It is already difficult.
Challenge accepted. 😜 -- Major Hayden
Attachment:
OpenPGP_0x737051E0C1011FB1.asc
Description: OpenPGP public key
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature
_______________________________________________ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
