On 10/13/25 18:26, jijinbei wrote:
I think the wording should be "legacy Perl and awk scripts /have to
be/ replaced" and this is the same requirement as for Meson.
I may have caused a misunderstanding here — *my proposal is not about
simply /replacing/ Perl or awk, but rather /rewriting/ the entire logic
into a cleaner and more maintainable form.*
Even if we move from Perl or awk to Python, if we retain the same
complex gbuild architecture, then the migration loses much of its purpose.
The goal is to simplify and clarify the build structure itself, not just
change the scripting language.
There is no misunderstanding. Having Perl and awk around is a stumbling
block on Windows. Moving those scripts to Python is a pre-requisite for
Meson migration.
You are welcome to contribute to this effort, see this report and the
commits toward it:
https://bugs.documentfoundation.org/show_bug.cgi?id=130911
As you can see from the discussion, it is crucial to be able to test the
translated scripts in practice with real data. Old bugs can be uncovered
and new ones introduced.
Ilmari
