@phnt @Suzu @amerika @bajax @ceooffuggy @f0x @hakui @j @mrsaturday @pwm @sicp @sun @tsubo

> That autohell takes an eternity to configure the project.

Sure.

> And that config.site is supposed to give a bunch of tested flag defaults to autohell so that it can use that instead of checking for every small thing that does not matter for the last 20 years.

0-1

Not even remotely. You're thinking of the *cache*. config.site supplies flags. So you set --without-qt6 in config.site instead of passing it to every configure script. Most stuff uses autotools. I don't like autotools, either, but cmakeninjameson is worse by miles.

> Ah, the Slackware meme of "you be the dependency resolver yourself".

0-2

No, this is not how that works. (In fact, the dependency tree is very easy to read or manipulate. Just typing `install` versus `depinst` gets you different things.)

> Congrats, you've just nuked every package with an optional dependency which I think crux supports.

0-3

No, I rm'd qt5 and qt6. They will not be built if the package doesn't exist. It's a dopey solution but you suggested a dopey problem. `find /usr/ports -name Pkgfile | xargs sed -i '/Depend/{s/qt[4-9] //}'`

> What about packages that have an optional GUI and a normal CLI. Gone.

0-4

It's fine if you do not have an interest in the topic but they have automated the process of pulling nonsense out of your ass, an LLM will now do that for free, so you don't have to say anything if you don't know.

> It's an issue a lot of people wanting to de-fluoride their OS have.

This is the worst possible way to go about that.

> (fuck bluez btw)

1-4

It's not technically a fact but I wanted for you to get at least one point.