<stenur>
I hope we stop to 3.7 soon. Source file renaming is such a great improvement!
<stenur>
s/stop/step/
<ppetrov^>
are we there yet
<stenur>
i think yes; doas will not replace sudo with 3.7, and nftables for iptables in core i really cannot imagine, i personally will not switch.
<stenur>
and more and more cmake for autotools i personally have no good opinion on either. Just today another fallout came in (#crux-devel).
<ppetrov^>
what's wrong with cmake?
<SiFuh>
I'd like to see an option with or without NINJA ;-) and some other things.
<braewoods>
You are talking about a problem that is primarily an upstream decision, that being the choice of build management software. All we can do is respond to it.
<braewoods>
We don't get to make that choice in general. So we just have to live with it.
<braewoods>
It's easier most of the time just to go along with their choice.
<SiFuh>
My reflux column arrived :-)
<SiFuh>
braewoods: for compilation? I agree.
<braewoods>
ppetrov^: nothing probably. I contribute to cmake projects from time to time though I would never choose it for new projects.
<braewoods>
ppetrov^: only autotools really gets any disdain from me.
<braewoods>
I suspect most projects using it don't even understand how it works. It's easier just to use something else like meson.
_moth_ has quit [Ping timeout: 240 seconds]
ty3r0x has joined #crux
ty3r0x has quit [Ping timeout: 268 seconds]
<stenur>
If upstreams have both why do i have to have to switch. Unless they say the one is legacy, maybe.
<stenur>
But you see that cmake recipes not rarely produce worse results or have missing pieces, like libmad.
<stenur>
There was a long discussion of cmake on FreeBSD last year, see for example