@navi Uuuh yeah *except* the ones meson depends on. (I know there's muon but then you'd have to hope for good compatibility with meson's dependencies… and I don't think I have that hope)
@navi Yeah that said 1:1 compatibility I'm not entirely sure, specially for complex buildsystems (like imagine if gcc would move to meson). (glibc is already done for in that area btw, hard-depends on python, so bootstraps are done with musl)
@lanodan i'm porting hiredict to meson and muon at the same time, and so far everything seems to be supported up to meson 0.61.0 (which is meson's lts with support to python 3.6 i think)
and i barely see projects going past 0.61.0 for now (and most still use 0.58), so i think i hope for the compat
@navi Meanwhile I think it's pretty important we move on from autohell in core projects. Specially since Jia Tan just proved how feasible it is to exploit the ./configure blob.
@lanodan ./configure is shipped with the tarball so you don't need the build system in your machine... except you still need make so...
shipping an auto-generated script that most people glance over is not the best idea
tho our other options are, raw make which not great for big things, cmake which, ew, and meson/muon -- out of those it'd either go with make or muon for core infra
@feld@lanodan@takao@navi I forget which software project it was but the main author had a huge anti-autotools rant that was passed around for years and I looked up his project and it uses autotools now.
@navi >shipping an auto-generated script that most people glance over is not the best idea Just add a bootstrap.sh script that autogenerates everything from the configure.ac file then.
@sun@feld@lanodan@navi Joerg Schilling had (rightfully) a hateboner for it until his death, it was fairly amusing. Then again, he would also have his makefiles vomit walls of text shitting on the user and introduce timeouts because you weren't using his variant of make.
@feld@takao@navi It's somewhat possible (I've done it for years), but I'd more recommend the musl-style configure script that spits out a `config.mk`.
At least 90% of what's in a configure script is useless cruft from the Unix wars. Like most projects aren't going to make any use of the workarounds for IRIX, pre-Solaris SunOS, … because their own code is likely not compatible at all (say if they use C11 or any somewhat recent POSIX functions).
@navi@feld@takao For me that's regular portability issues, specially when you're at the level of core projects where you're going to hit various kinds of weird deviations between systems.
i think a major issue is people (like me) who mainly runs linux, usually glibc linux, and is not aware of the differences needed to build in different unixes
sure i'm picking them up now over time, but having a system that already deals with them for me helps avoiding reinventing the wheel one piece at a time
autotools tho... yeah you don't need 90% of the checks
@navi@feld@takao Which also reminds me of seeing https://cgit.freebsd.org/src/tree/bin/test/tests/legacy_test.sh and the sheer simplicity of it while still being TAP-compliant triggered me in the process of throwing out ATF from utils-std (which I'd see as good, specially as Kyua which it depends on was segfaulting on Haiku).