<r0ni>
so the moral of the story i read above is elogind is bloat (yes) but it's needed for things and is completely optional anyway, makes me want to look at it even more. But alas, I know it's like 99% all systemd code, also makes me want to stay away
<r0ni>
but i can't resist a good challenge
<r0ni>
wow that kde repo is massive
<r0ni>
impressive
<SiFuh>
Yes, hope he is proud of it
<r0ni>
my xfce repo looks like junk comparing lol
<r0ni>
i gotta step it up, it seems
<farkuhar>
does anyone else find that after a rust version bump, the old sccache artifacts are no longer usable? Clearing out the contents of ~/.cache/sccache finally managed to stop the error message "this compiler cannot create executables".
<farkuhar>
I guess that's the expected consequence of updates to a fast-moving language. Still, if the language updates arrive more frequently than updates to software written in rust, it kind of defeats the purpose of sccache.
<cruxbot>
[contrib.git/3.7]: libplacebo: updated to 6.292.0
<cruxbot>
[contrib.git/3.7]: mpv: updated for new libplacebo
<cruxbot>
[opt.git/3.7]: qtwebengine: fixed build if re2 is installed
ppetrov^ has quit [Quit: Leaving]
<ukky>
r0ni: there is no harm in adding elogind as dependency even for xorg-server, or any other port. But for xorg-server the dependency should be made optional.
<farkuhar>
in case tsaop follows the chat logs (as dlcusa has been known to do), here's a more flexible Pkgfile for the crux-kf5/sddm port (which as of version 0.20 can also build against qt6): http://ix.io/4ALO
<farkuhar>
unfortunately there's no way to grant similar flexibility to the footprint file, the way we do by replacing lib/modules/$(uname -r) with lib/modules/<kernel-version>. So maybe in this case it would be better to make sddm-qt6 a separate port.
<jaeger>
he's responsive to pull requests, for reference