02:45 <remiliascarlet> System without xorg is just broken.

02:46 <remiliascarlet> Unless it's TTY.

04:17 <jaeger> I have a wayland-only gaming system that works pretty well, for what that's worth

05:04 <remiliascarlet> I can't get Fcitx to work on Wayland, so there's no point to me to use something that doesn't even allow me to write in my native language.

05:07 <remiliascarlet> And I don't really like the fact that Wayland lets each compositor decide where things like environment variable are defined, and they're mostly put under /etc/environment, which therefore applies to all users whether they like it or not.

05:32 <sajcho> remiliascarlet: https://fcitx-im.org/wiki/Using_Fcitx_5_on_Wayland

06:00 <remiliascarlet> sajcho: Website seems to be down.

07:16 <sajcho> Hmm,  I open the page normally.

07:22 <remiliascarlet> Now it works for me too.

07:27 <remiliascarlet> I put these environment variables everywhere, and still doesn't work.

07:28 <remiliascarlet> The "Support in Wayland Compositor" session really shows to me how much of a mess this whole protocol is.

07:30 <remiliascarlet> "I just made this program, but now I have to keep in mind 16 different Wayland compositors, in addition to Xorg. However, Xorg is a mess, so drop it, it's somehow a lot easier to maintain code for 16 different ever changing compositors than it is to maintain code for 1 display server that didn't change over the last 40 years."

18:01 <cruxbot> [opt.git/3.7]: poppler: fix depedencies, FS#1936

18:01 <cruxbot> [opt.git/3.7]: qpdf: update to 11.8.0

18:30 <cruxbot> [opt.git/3.7]: firefox-bin: update to 121.0.1

18:51 <serpente> hello cruxter friends

18:52 <serpente> i just set up a repo for some orphan ports that i will maintain

18:52 <serpente> can i get an crux.nu account? cant find a register page...

18:53 <serpente> so i can put the ports httpup links there

18:53 <serpente> https://codeberg.org/serpent/crux

19:20 <jaeger> Hello, you can find the register page here for ports repos: https://crux.nu/portdb/?a=register

19:25 <serpente> thanks jaeger

19:29 <jaeger> No problem. I'll verify and add it today if I can, currently working

19:32 <serpente> perfect, take you time

19:32 <serpente> repository name can be anything?

19:47 <jaeger> No official restriction, it's common to be your username

19:48 <jaeger> And it can be changed later if needed

19:58 <serpente> ok

20:13 <ppetrov^> jaeger, would you be interested to add a ports repo for R modules?

20:14 <ppetrov^> I have been maintaining and expanding one, after I wrote myself cran2crux (same idea as for cpan2crux, but for R).

20:14 <ppetrov^> https://github.com/slackalaxy/crux-ports/tree/main/r4-modules

20:16 <ppetrov^> few remarks: I am not removing any documentation. It sits in /usr/lib/R and it is important if you want to know how a new package's functions work. It also includes vignettes and other stuff, so prtveryfy always returns "WARN"

20:17 <ppetrov^> some deps may be a bit redundant (not circular!), because deps info is first extracted from CRAN or BioConductor and then I additionally search for deps outside the R eco system

20:18 <ppetrov^> and finally, I am still hesitant about naming. R is at major version 4 right now and is expected to stay like this in the following years. So, names are like r4-module, unlike arch or debian (r-module). I thought it looks similar to the p5-module names

20:19 <ppetrov^> sorry for the spam, i am open to suggestions

22:28 <jaeger> I will add it to the repo list if you want to publish it. I haven't used R myself in years (last job), though, so I don't have a stake in it

23:14 <ppetrov^> jaeger, I will be doing some massive additions to it, so after that I'll let you know. probably to the end of the week. Just wanted to make sure that a repo with all ports having a warning (because of docs) is not critical