On Sat, Mar 30, 2024 at 11:53:07AM -0400, Neal Gompa wrote: > On Sat, Mar 30, 2024 at 11:36 AM Zbigniew Jędrzejewski-Szmek > <zbyszek@xxxxxxxxx> wrote: > > > > On Sat, Mar 30, 2024 at 10:02:42AM -0500, Michael Catanzaro wrote: > > > On Sat, Mar 30 2024 at 02:55:21 PM +00:00:00, Zbigniew Jędrzejewski-Szmek > > > <zbyszek@xxxxxxxxx> wrote: > > > > CMake for many years fought against pkgconf and pushed people towards > > > > copying those scripts into sources. It is still very common for projects > > > > using CMake to come with a whole directory of badly written detection > > > > scripts that each replace a single-line pkgconf invocation. > > > > > > > > And of course nobody has time to look into those scripts, making it > > > > easy to smuggle something through there. > > > > > > It's still better than Autotools, though. If a project doesn't want to > > > switch to Meson for whatever reason, then CMake is a reasonable alternative. > > > > > > I agree that CMake is not as good as Meson, and that CMake find modules are > > > inferior to pkg-config. > > > > But then we shouldn't describe them as equivalent alternatives ;) > > If we say "switch to a modern build systemd, e.g. cmake or meson", > > people will randomly choose on or the other and since the whole CMake > > ecosystem is built around find modules, we'll end with a bazillion of > > those. > > > > Instead we should say: "Use meson. If you can't for some reason, consider > > CMake, but come talk to us first." > > > > Meson's own module instability and lack of extensibility make it > unsuitable for a wide range of projects, especially complex ones. The > lack of stability in Meson itself is so bad that Meson upgrades break > GNOME, libvirt, and others. And the lack of extensibility is an > anti-feature. It means that Meson cannot scale to the infinite world > of project needs because everything has to be bent around it or hacks > need to be written in the projects to work around its weaknesses. > > No way would I personally recommend it. I'm not going to go as far as > to recommend one explicitly over the other from a distribution > perspective, but personally I would never choose Meson anymore. Also we haven't found the meson lead developer to be very open to fixing an obvious bug that affects Fedora/RISC-V, even after providing and carefully testing a patch for it. It wasn't encouraging. Rich. > > > > -- > 真実はいつも一つ！/ Always, there's only one truth! > -- > _______________________________________________ > 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 -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com nbdkit - Flexible, fast NBD server with plugins https://gitlab.com/nbdkit/nbdkit -- _______________________________________________ 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
