Hi - > [...] > > My idea is to split systemtap-sdt-devel into two packages: one with all the > > content but without the python script (/usr/bin/dtrace) and a new one > > containing only the mentioned script. No objection here. > > [...] > > I also did a test rebuild of all packages directly build-requiring > > systemtap-sdt-devel and identified these packages that really need the > > dtrace script: glib2, sssd, qemu, python2.7, postgresql15, postgresql16, > > perl, php, mariadb10.11, and libvirt. Those would newly depend on a new > > package where we move the script to. (The logistic challenge there will be side-tag rebuilding all those after a systemtap subrpm split.) How much time did excluding the python bits from the perl buildroot actually save during your tests? > Unanswered question is run-time dependencies. There might be packages which > run-require systemtap-sdt-devel because of dtrace executable: > > # dnf -q -C repoquery --whatrequires systemtap-sdt-devel > lttng-ust-devel-0:2.13.8-1.fc41.x86_64 > perl-devel-4:5.38.2-507.fc41.x86_64 > systemtap-testsuite-0:5.1~pre17062192g5fd8daba-1.fc40.x86_64 By default, these packages could inherit dependencies on both of the split subrpms, until their respective packagers decide to analyze and narrow it further down. - FChE -- _______________________________________________ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
