autotools to meson: policy?

[Enrico Weigelt, metux IT consult]

On 14.12.24 08:06, tlaronde at kergis.com wrote:
> I still liked to have a Xorg developers' expressed policy about these
> points:
>
> - Has the meson framework to provide at least the configuration
> flexibility provided by autotools, so that whoever is compiling Xorg
> could, in the future, configure it the way it managed to do with
> autotools?

[speaking just for the Xserver and drivers]

IMHO (for our cases) yes. But we maybe should upgrade to a newer
version, where things can be a done a bit easier, esp. dependencies
between config flags.

There's still a lot cleanup work to be done here, anyways.

> - What to do when python byte-compiling is involved?

Do we have that case ?

> *: for this, I have chosen for xcbproto (I know: it depends on another
> church) to provide POSIX.2 scripts to search for python and to
> byte-compile, allowing to use the scripts also at install time and
> allowing OSes not using python (and hence not using meson) to be able
> to do things.

Do we really need to do bytecode compilation here ?

IMHO, most distros already have their own generic mechanism. As upstream
we really can't know which bytecode / python engine types and versions
are used on a particular distro/target, so IMHO we shouldn't care at
all, instead just install the .py files and leave the rest to the distro.


--mtx

--
---
Hinweis: unverschlüsselte E-Mails können leicht abgehört und manipuliert
werden ! Für eine vertrauliche Kommunikation senden Sie bitte ihren
GPG/PGP-Schlüssel zu.
---
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info at metux.net -- +49-151-27565287