jaeger changed the topic of #crux-devel to: CRUX (https://crux.nu/) development channel | Logs: https://libera.irclog.whitequark.org/crux-devel/
farkuhar has left #crux-devel [#crux-devel]
SiFuh has quit [Ping timeout: 272 seconds]
SiFuh has joined #crux-devel
groovy2shoes has quit [Ping timeout: 260 seconds]
SiFuh_ has joined #crux-devel
SiFuh has quit [Ping timeout: 260 seconds]
groovy2shoes has joined #crux-devel
SiFuh_ has quit [Ping timeout: 245 seconds]
SiFuh has joined #crux-devel
groovy2shoes has quit [Remote host closed the connection]
groovy2shoes has joined #crux-devel
<stenur> nghttp2 is "long" on .47 btw
<stenur> aka libnghttp2 as it is now called
<stenur> maybe not that important though, in the last months (before i stopped tracking) they mostly cared for their webserver and HTTP/3; from the linked things i see a bug that could affect us
farkuhar has joined #crux-devel
<stenur> Btw having a libxml2 .MAJOR.MINOR symlink would be tremendous, i had to rebuild it all (and clang still missing) as we only have .MAJOR.MINOR.UPDATE and the normal .so is never kept as such by linking (do not ask me no questions.
braewoods has quit [Quit: WeeChat 2.8]
braewoods has joined #crux-devel
jue has joined #crux-devel
jue has joined #crux-devel
<jue> stenur: I agree, we should have a "libxml2.so.2" symlink, looks like we lost that while swiching to the cmake build
<farkuhar> beerman: the upower build error seems to arise whenever libxslt is installed, even with the meson option -D gtk_doc=false. Your lxc containers never had libxslt (especially after running pkg-clean), so you never encountered the errors that SiFuh and jaeger reported.
<beerman> farkuhar: I can't check right now but I am pretty certain I have libxslt installed on my machines
<farkuhar> I managed to build upower successfully, after removing libxslt (despite the 29 packages that depend on it).
<beerman> i can run a quick test in my container
<farkuhar> it's a peculiar combination that creates this error. I think it needs libxslt installed, but gtk-doc NOT installed, and then the meson setup fails.
<beerman> rip me..
<beerman> i can reproduce the build error that way. alternative a) depend on gtk-doc (nobody likes that) b) hack around it (no maintainer likes that)
<farkuhar> alternative a) is what I proposed to Romster, after first reproducing SiFuh's error last weekend. I can see why it's not a popular choice.
<beerman> no matter what you do you can't please everybody (and for me, I am done with that anyway). Alternative c) disable manpages as well btw ;)
<groovy2shoes> alternative d) screw meson ¬_¬
<beerman> alternative e) if you are not contributing stop posting in this channel?
<beerman> all you ever do groovy2shoes is hate around against things.
<farkuhar> Among the stale files in the old source array (before beerman's cleanup) was a manpage. Maybe that was included in the ports tree because alternative c) was considered too drastic.
<beerman> The only thing too drastic in it that I can see is that people can't get over the fact that the world keeps spinning, with or without them
jue has quit [Read error: No route to host]
jaeger has quit [Quit: leaving]
<stenur> btw on FreeBSD i saw the commit "zstd: build with C11 [.] This enables thread-aware timers which in turn fixes benchmark result reports."
<stenur> (aka -std=c11)
<stenur> (dunno (yet) whether it matters for Linux, a short git grep in the code made me sceptical though)