<beerman>
oof, i went harder into shutdown then expected when you look at the glu-32 spectacle
<farkuhar>
Re: FS#1924, I don't fully understand the reluctance to keep the xorg collection enabled, even when setting up a headless host. Flexible Pkgfiles are a useful ideal, but the resulting breakage from disabling an official repo is not something that port maintainers should have to accommodate.
<beerman>
it looks like its effectively missing xcb bindings and qtx11extras (as reported by qownnotes)
<farkuhar>
beerman: thanks for the footprint diff. So dropping the xkeyboard-config dependency resulted in two missing components from qt5 (and I'd assume qt6-base is similarly affected).
<beerman>
i do like having x11 optional, even though one of my wayland clients has xwayland enabled, we just need to make it so that there is no problem enabling either one or both (or none)
<beerman>
yeah
<beerman>
things like that should be easier to prepare in a pull request once we have gitea in place
<farkuhar>
for the next version of the handbook, should we include a warning like "If you disable one of the official repos, do not expect ports to build successfully"? While alexmat has been around CRUX long enough to know the effects of such changes, a first-time user might benefit from stronger wording than what the handbook currently has.
<beerman>
xorg is not enabled by default though, is it?
<beerman>
its just that certain ports require things from xorg repo for example
<beerman>
so in case you install $certainports you'll need to have xorg repository enabled
<farkuhar>
xorg is enabled by default, if I recall correctly from my last fresh install. What alexmat did on his headless host is non-standard practice, which could only result from alexmat deliberately overriding the installed defaults.
<beerman>
you are right, it is
<jaeger>
Yeah, only contrib and compat-32 are disabled by default
<beerman>
in any way, i'd see it as a goal to have x11 optional as well. i am not unhappy that we are doing it now, but its not quite right yet