On Mon, Apr 15, 2024 at 11:10:28AM +0200, Miroslav Suchý wrote: > Dne 13. 04. 24 v 1:16 odp. Zbigniew Jędrzejewski-Szmek napsal(a): > > The proposal explicitly states that we don't want Perl in all buildroots. > > How many seconds we save by NOT pulling Perl? Per each build? In total for whole release cycle? > > How many seconds we loose (lost) by refactoring the code? I wasn't measuring the time exactly, but about two weeks of my time. > And syncing with Debian? > Or even worse finding issues that Debian will find and we not? Some divergence from Debian would happen anyway. Their build system is different enough that we have some non-overlapping issues. And in my implementation, I was a bit more conservative in what is changed, doing the minimal replacements. We'd either have to maintain some patches or wait until upstream accepts our changes and makes a release. Having a tool that is under our control allows us to update much more quickly. For Perl, the issue is not so much the seconds and megabytes, but that a) Perl is now effectively a niche language, we made the choice to use Python for tooling instead a long time ago, and b) it'd pull in the interpreter and a set of modules. Considering that we need python marshalparser for the pyc files, that'd mean two interpreter stacks in some cases. Perl certainly has and will have its uses, but I don't think we should use it when adding completely new tooling to our build system. Zbyszek -- _______________________________________________ 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
