💾 Archived View for gemini.ctrl-c.club › ~phoebos › logs › freenode-kisslinux-2020-03-03.txt captured on 2024-05-12 at 16:09:02.
⬅️ Previous capture (2021-12-17)
-=-=-=-=-=-=-
2020-03-03T00:03:44 #kisslinux <E5ten> looks like a test is the part failing there so try -DHB_BUILD_TESTS=OFF
2020-03-03T00:11:06 #kisslinux <adamantium[m]> What am I suppose to do with something like this amazon recruiter's message? https://termbin.com/zqum I do need a job but idk if I'm good enough for amazon "machine learning", is that just a mass message?
2020-03-03T00:12:15 #kisslinux <adamantium[m]> Would appreciate feedback from you guys on that
2020-03-03T00:16:28 #kisslinux <fehawen> adamantium[m]: Hard to tell if it's a mass email, but based on what I know of Amazon's recruitment tactics in Sweden it isn't a mass message.
2020-03-03T00:16:45 #kisslinux <konimex> hmm... harfbuzz .so doesn't have that SONAME
2020-03-03T00:16:51 #kisslinux <konimex> with cmake
2020-03-03T00:17:26 #kisslinux <konimex> and linking them manually is ugly
2020-03-03T00:17:46 #kisslinux <fehawen> adamantium[m]: Sure, they contact a LOT of people, but they have teams and teams of recruiters who's only job is to hunt for candidates on github, linkedin, etc etc
2020-03-03T00:18:53 #kisslinux <fehawen> And based on the number of people they hire, there'd be no reason for them to expect every candidate to be a super senior developer.
2020-03-03T00:19:41 #kisslinux <fehawen> And even if that were the case, I'd send him a reply and hope for an interview as it'll be a great learning experience no matter how it goes
2020-03-03T00:20:18 #kisslinux <adamantium[m]> Ok, well I only leave half-day's drive from seattle, it's not unthinkable living there.
2020-03-03T00:20:46 #kisslinux <adamantium[m]> I guess I will reply and be honest, though, to ensure we're not wasting each others time here.
2020-03-03T00:21:27 #kisslinux <fehawen> Sure, be honest, that always pays off. But don't sell yourself short.
2020-03-03T00:21:30 #kisslinux <adamantium[m]> I do not believe it is fake, but I wonder if I am just a needle in a haystack
2020-03-03T00:21:59 #kisslinux <adamantium[m]> Ok thank fehawen
2020-03-03T00:24:01 #kisslinux <fehawen> Companys like Amazon, and many of the other big players, don't want to waste too much time on job applications and "waiting" for the right candidates to come around. That's why they have these teams of recruiters who scour the internet for viable candidates.
2020-03-03T00:25:30 #kisslinux <fehawen> You're not a needle in a haystack, it's more of long shot from their side as much as from yours. They see some potential in you, but they know very little about you (and most other candiates), so they call in all candidates they can find for interviews.
2020-03-03T00:26:05 #kisslinux <fehawen> Meaning you're not "special" in any way yet, but they don't know that yet, that's why they want to set up an interview to find out.
2020-03-03T00:26:17 #kisslinux <fehawen> Sorry for the spamming btw :P
2020-03-03T00:28:23 #kisslinux <fehawen> And as you said, be honest about your shortcomings, but also make sure to tell them all the things you're great at and know a lot about.
2020-03-03T00:30:05 #kisslinux <fehawen> Any open source projects you might've contributed to etc, be sure to tell them about it because they love to hear it as it shows you're passionate about what you do and like to share that with others
2020-03-03T00:32:06 #kisslinux <fehawen> Any company looking to hire developers aren't necessarily looking for the most competent or knowledge individuals, but rather the most passionate individuals.
2020-03-03T00:32:28 #kisslinux <fehawen> And I'll shut up now lol
2020-03-03T00:33:31 #kisslinux <dilyn> Did icyphox ever resolve his bizarre kernel bug??
2020-03-03T00:37:36 #kisslinux <E5ten> konimex: forgot about the harfbuzz SONAME thing, have something for it like with curl http://ix.io/2dem
2020-03-03T00:49:21 #kisslinux <adamantium[m]> ty fehawen
2020-03-03T00:49:32 #kisslinux <adamantium[m]> Off to the belly of the beast then
2020-03-03T00:50:39 #kisslinux <adamantium[m]> konimex: any idea why my system doesn't want to build 'go' ? It must be becausae i dont have busybox. The error says go tool dist: mkdtemp(/var/tmp/go-cbuild-XXXXXX): No such file or directory
2020-03-03T00:50:47 #kisslinux <adamantium[m]> I do not have "mkdtemp" on my path, should I/
2020-03-03T00:50:48 #kisslinux <adamantium[m]> ?
2020-03-03T00:51:14 #kisslinux <konimex> two secs, let me check if my system has mkdtemp
2020-03-03T00:51:35 #kisslinux <adamantium[m]> i think it's a shell feature, isn't it?
2020-03-03T00:52:03 #kisslinux <konimex> nope, no mkdtemp in busybox, but as for shell, go uses bash
2020-03-03T00:52:48 #kisslinux <adamantium[m]> okay ... argh
2020-03-03T00:52:56 #kisslinux <adamantium[m]> I rebuilt my entire system recently, only go fails
2020-03-03T00:53:04 #kisslinux <adamantium[m]> I have never tried to build go before either
2020-03-03T00:53:25 #kisslinux <adamantium[m]> Any ideas for more trouble shooting?
2020-03-03T00:53:56 #kisslinux <konimex> I'd suggest building it manually to see if it errors out too and set -x the make.bash file to trace it down
2020-03-03T00:55:17 #kisslinux <konimex> hmm... since freetype-harfbuzz is volatile and kiss doesn't support separate patches sources (so I'd have to keep up with kiss), I'd have to cat <<EOF it directly in the build file
2020-03-03T00:55:26 #kisslinux <konimex> brb
2020-03-03T00:59:39 #kisslinux <E5ten> mkdtemp is a function not a command...
2020-03-03T01:02:27 #kisslinux <E5ten> konimex: you still need libgcc_s at runtime for the stage0 for rust right?
2020-03-03T01:02:35 #kisslinux <E5ten> well libgcc_s.so.1
2020-03-03T01:02:38 #kisslinux <konimex> needed, but not anymore
2020-03-03T01:02:51 #kisslinux <E5ten> how'd you get around it?
2020-03-03T01:03:41 #kisslinux <E5ten> also, what's your file list for e2fsprogs?
2020-03-03T01:04:04 #kisslinux <konimex> basically I "make dist" it and use the resultant tarball for future rust build
2020-03-03T01:04:26 #kisslinux <konimex> had to do some export shenanigans though for LD_LIBRARY_PATH
2020-03-03T01:05:49 #kisslinux <konimex> the newly-produced tarball becomes the new stage0
2020-03-03T01:05:51 #kisslinux <konimex> e2fsprogs: https://termbin.com/dmwm
2020-03-03T01:05:57 #kisslinux <konimex> whoops
2020-03-03T01:06:01 #kisslinux <konimex> e2fsprogs: https://termbin.com/dwmw
2020-03-03T01:10:02 #kisslinux <E5ten> if you run configure like _cv_gnu_make_command='' ./configure, and use libs and progs as your make targets, and install-libs-recursive and install-progs-recursive as your make install target, you should be able to use bmake I think
2020-03-03T01:20:12 #kisslinux <sirtomato> hello
2020-03-03T01:29:41 #kisslinux <fehawen> sirtomato: Good evening/night
2020-03-03T01:29:59 #kisslinux <fehawen> Or dawn, rather, at least where I am heh
2020-03-03T01:48:36 #kisslinux <adam1111> hey everyone so I tried following the guide here https://k1ss.org/wiki/WiFi-connection-with-wpa_supplicant to set up dhcpcd hooks + wpa_supplicant but it doesn't seem to actually execute the hook
2020-03-03T01:48:56 #kisslinux <adam1111> however if I stop dhcpcd, run wpa_supplicant manually, and then run dhcpcd wlan0, everything is ok
2020-03-03T01:51:04 #kisslinux <adam1111> I've linked the hook into /usr/libexec/dhcpcd-hooks/
2020-03-03T02:00:32 #kisslinux <konimex> dhcpcd hooks are hit and miss
2020-03-03T02:00:43 #kisslinux <konimex> just run both of them manually
2020-03-03T02:05:57 #kisslinux <adam11111> konimex if I added both commands to a script what's the best way to execute it on startup
2020-03-03T02:06:16 #kisslinux <konimex> personally, I use runit services for both
2020-03-03T02:06:31 #kisslinux <adam11111> oh so you created a service to start wpa_supplicant?
2020-03-03T02:07:06 #kisslinux <konimex> yep
2020-03-03T02:07:10 #kisslinux <adam11111> ah
2020-03-03T02:07:17 #kisslinux <adam11111> how do you ensure it runs before dhcpcd?
2020-03-03T02:07:40 #kisslinux <konimex> I don't
2020-03-03T02:08:17 #kisslinux <adam11111> and it's happy that way? from what I can tell, if dhcpcd is running and then I run wpa_supplicant, I have to restart dhcpcd for things to work
2020-03-03T02:08:34 #kisslinux <konimex> well, my laptop certainly is happy that way
2020-03-03T02:08:43 #kisslinux <adam11111> weird
2020-03-03T02:08:53 #kisslinux <adam11111> I've also noticed I can't just run dhcpcd, I have to run dhcpcd {interface}
2020-03-03T02:09:14 #kisslinux <adam11111> otherwise it throws an error about finding no interfaces
2020-03-03T02:09:20 #kisslinux <konimex> yep that's on my runitscript too
2020-03-03T02:09:25 #kisslinux <adam11111> gotcha
2020-03-03T02:09:30 #kisslinux <adam11111> I'll give it a shot and see if it works
2020-03-03T02:09:34 #kisslinux <adam11111> thanks for the advice!
2020-03-03T02:10:32 #kisslinux <konimex> make sure to not daemonize it if you're running it on runit (e.g. use dhcpcd -B)
2020-03-03T02:27:29 #kisslinux <fehawen> Night night
2020-03-03T02:56:06 #kisslinux <adam1111> konimex that worked thank you
2020-03-03T03:47:02 #kisslinux <revbo> Hey all, quick question. I've been using KISS for a few weeks and really dig it, would like to contribute to packaging but I refuse to use GitHub. Is there an alternative way to contribute, like git email?
2020-03-03T04:00:49 #kisslinux <konimex> you can e-mail to dylan with the patches necessary
2020-03-03T04:09:10 #kisslinux <revbo> Excellent, thank you.
2020-03-03T04:50:23 #kisslinux <grexilo> hi
2020-03-03T05:21:45 #kisslinux <adamantium[m]> But how can you download updates without using github, or do we have alternate mirrors?
2020-03-03T05:52:51 #kisslinux <adamantium[m]> Anyone wanna help me patch the latest libcap? it is failing with undefined reference to `pthread_yield'
2020-03-03T05:53:32 #kisslinux <adamantium[m]> Apparently, we should be able to replace pthread_yield with sched_yield
2020-03-03T05:53:34 #kisslinux <adamantium[m]> But I don't know C
2020-03-03T05:59:54 #kisslinux <adamantium[m]> https://github.com/kisslinux/community/issues/495
2020-03-03T06:24:48 #kisslinux <adamantium[m]> https://github.com/kisslinux/community/pull/496
2020-03-03T06:24:52 #kisslinux <adamantium[m]> I think I got it
2020-03-03T06:37:34 #kisslinux <mforney> you should send the patch upstream
2020-03-03T06:37:48 #kisslinux <adamantium[m]> Hi mforney , wow really?!
2020-03-03T06:37:53 #kisslinux <adamantium[m]> I don't even know C
2020-03-03T06:37:56 #kisslinux <adamantium[m]> Are you sure?
2020-03-03T06:39:03 #kisslinux <adam11111> I'm having trouble starting X. I've got xorg-server installed but when I try to start X it says it can't find /dev/dri/card0. I'm running intel iris graphics. anyone else get it working with the same builtin graphics?
2020-03-03T06:39:33 #kisslinux <adam11111> when I google the problem the most common error seems to be missing xorg-server...but I have that installed
2020-03-03T06:40:24 #kisslinux <mforney> adamantium[m]: yeah, the man page for pthread_yield says to use sched_yield instead, and if you look at glibc implementation, it's just a wrapper around sched_yield (https://sourceware.org/git/?p=glibc.git;a=blob;f=nptl/pthread_yield.c;h=57d103cb388a00a8a0f7c4ce6cccaa83744b2235;hb=HEAD)
2020-03-03T06:40:37 #kisslinux <adamantium[m]> okay cool! thanks
2020-03-03T06:43:11 #kisslinux <mforney> adam11111: sounds like you don't have the proper DRM driver enabled in your kernel
2020-03-03T06:43:32 #kisslinux <adamantium[m]> mforney: I wonder if I should remove the include for the pthread header, too, or just leave it?
2020-03-03T06:43:40 #kisslinux <adam11111> mforney. do I need to enable something even if I'm just using the modesetting driver?
2020-03-03T06:44:05 #kisslinux <mforney> adamantium[m]: that depends on if the file uses anything else from pthread.h
2020-03-03T06:45:15 #kisslinux <adamantium[m]> mforney: I see, well I see a gazillion uses of the word pthread, so it stays. Thanks
2020-03-03T06:45:51 #kisslinux <mforney> adam11111: yes, modesetting is done through DRM
2020-03-03T06:47:33 #kisslinux <adam11111> mforney ok I'll check menuconfig and rebuild my kernel when I find the option i need
2020-03-03T06:47:34 #kisslinux <adam11111> thank you
2020-03-03T06:56:22 #kisslinux <adamantium[m]> mforney: https://bugzilla.kernel.org/show_bug.cgi?id=206741 < I used your wording, and appreciate you for giving me that pointer. I really want to get better at all of this stuff, it means a lot that you help me with this and build my confidence to work harder and study more
2020-03-03T06:57:16 #kisslinux <adam11111> mforney: no dice :(. drm was actually already compiled into the kernel but just to test I installed them as modules instead. then rebooted and ran `modprobe i915` and checked that `i915` and `drm` were loaded. tried running X and it still said no screens found/no /dev/dri/card0
2020-03-03T06:59:02 #kisslinux <adam11111> I also just tried loading the drm module without the intel module, same issue
2020-03-03T07:01:00 #kisslinux <mforney> adamantium[m]: no problem. the best way to learn is by doing, and i'm happy to offer guidance
2020-03-03T07:03:41 #kisslinux <mforney> adam11111: hmm... well, you definitely need /dev/dri/card0 for xf86-video-modesetting to work. are there any clues in dmesg?
2020-03-03T07:04:03 #kisslinux <adam11111> checking dmesg
2020-03-03T07:07:37 #kisslinux <adam11111> nope nothing in dmesg
2020-03-03T07:46:41 #kisslinux <dylanaraps> adamantium: Do you have write permissions to /var/tmp?
2020-03-03T07:46:48 #kisslinux <dylanaraps> As a normal user.
2020-03-03T07:48:12 #kisslinux <dylanaraps> adam11111: If the file doesn't exist it's a kernel driver issue. If it does exist it's a permissions issue.
2020-03-03T07:48:17 #kisslinux <adamantium[m]> dylanaraps: no i do not, should i
2020-03-03T07:48:38 #kisslinux <dylanaraps> drwxrwxrwt 3 root root 4096 Mar 3 09:45 /var/tmp
2020-03-03T07:48:57 #kisslinux <adamantium[m]> ls: cannot access '/var/tmp': No such file or directory
2020-03-03T07:49:01 #kisslinux <dylanaraps> In baselayout: install -dm 1777 "$1/var/tmp"
2020-03-03T07:49:21 #kisslinux <adamantium[m]> i do not have baselayout installed
2020-03-03T07:49:29 #kisslinux <dylanaraps> When you ran `kiss r baselayout` it probably removed it as it was empty.
2020-03-03T07:49:36 #kisslinux <adamantium[m]> makes sense
2020-03-03T07:49:46 #kisslinux <adamantium[m]> Can we fix this to help others?
2020-03-03T07:49:56 #kisslinux <dylanaraps> This is why I told you to just rm the /var/db/kiss/installed/baselayout dir
2020-03-03T07:50:07 #kisslinux <dylanaraps> Instead of 'kiss r baselayout'
2020-03-03T07:50:08 #kisslinux <adamantium[m]> Ah
2020-03-03T07:50:13 #kisslinux <dylanaraps> This isn't a kiss bug
2020-03-03T07:50:18 #kisslinux <adamantium[m]> I see
2020-03-03T07:50:35 #kisslinux <dylanaraps> Your solution is to just create the dir.
2020-03-03T07:50:40 #kisslinux <dylanaraps> Or set TMPDIR to /tmp
2020-03-03T07:50:48 #kisslinux <adamantium[m]> Well now go is building
2020-03-03T07:50:53 #kisslinux <adamantium[m]> That's reassuring
2020-03-03T07:50:57 #kisslinux <dylanaraps> Yes
2020-03-03T07:51:01 #kisslinux <dylanaraps> It'll work now
2020-03-03T07:53:36 #kisslinux <adamantium[m]> Ok, thanks. I reported the fix and closed the issue, just incase someone else hits it in the future
2020-03-03T07:55:22 #kisslinux <adamantium[m]> By the way, dylanaraps , libcap fails to build if 'go' is installed on a kiss system. https://termbin.com/n1hq < something I noticed this morning
2020-03-03T07:55:54 #kisslinux <adamantium[m]> There is no "configure" to disable 'go' features of libcap, whatever that may be, so what is best way to fix this :D
2020-03-03T08:01:06 #kisslinux <dylanaraps> adamantium: make GOLANG=no
2020-03-03T08:01:42 #kisslinux <adamantium[m]> ah, I was just about to do another sed to Make.Rules
2020-03-03T08:01:46 #kisslinux <adamantium[m]> Cool
2020-03-03T08:02:03 #kisslinux <adamantium[m]> sed -i "s/GOLANG /#GOLANG /" Make.Rules
2020-03-03T08:02:05 #kisslinux <adamantium[m]> lol
2020-03-03T08:10:18 #kisslinux <adamantium[m]> dylanaraps: with GOLANG=no it no longer fails related to go, but fails with missing file operand ??? https://termbin.com/e81e -- when I remove the GOLANG=no line, it builds fine (sans go installed, that is)
2020-03-03T08:10:58 #kisslinux <adamantium[m]> NEVER MIND
2020-03-03T08:11:05 #kisslinux <adamantium[m]> lol
2020-03-03T08:23:11 #kisslinux <dzove855> dylanaraps: huu, you removed the @ n autocomplet? nice!
2020-03-03T08:24:29 #kisslinux <dylanaraps> Yeah
2020-03-03T08:24:45 #kisslinux <dylanaraps> It's just dzo<TAB> now
2020-03-03T08:24:51 #kisslinux <dylanaraps> Also adds the colon
2020-03-03T08:25:06 #kisslinux <dzove855> yeah i have seen. It's great
2020-03-03T08:25:40 #kisslinux <dzove855> i have seen that the autocomplet does not work on commands
2020-03-03T08:26:49 #kisslinux <dylanaraps> It does not
2020-03-03T08:26:57 #kisslinux <dylanaraps> How it works is through abuse of files
2020-03-03T08:27:12 #kisslinux <dylanaraps> Each nick and channel is a file in the tmpdir.
2020-03-03T08:27:26 #kisslinux <dylanaraps> Files can't contain '/' which makes this tricky for commands. ;)
2020-03-03T08:27:48 #kisslinux <dylanaraps> bash hardcodes the readline completion type to file based fyi.
2020-03-03T08:28:10 #kisslinux <dzove855> yep i know. i have seen how it is hardcoded but didn't know why it is done like this..
2020-03-03T08:28:15 #kisslinux <dzove855> it's worth asking why
2020-03-03T08:29:25 #kisslinux <dylanaraps> It was changed in bash 2.0.5 iirc
2020-03-03T08:30:32 #kisslinux <dzove855> i had 5years back when it was done haha probably they have seen, taht i would break something with it..
2020-03-03T08:30:46 #kisslinux <dzove855> s/taht/that/
2020-03-03T08:34:07 #kisslinux <dylanaraps> heh
2020-03-03T08:36:55 #kisslinux <dzove855> dylanaraps: did you have an idea how this could be done more elegant instead of using eval: https://github.com/dzove855/bin/blob/master/bin/bee
2020-03-03T08:38:04 #kisslinux <dylanaraps> Interesting
2020-03-03T08:43:28 #kisslinux <adamantium[m]> dylanaraps: I switched libcap to mk()
2020-03-03T08:52:09 #kisslinux <dzove855> dylanaraps: i dunno why, in bash, sometimes you can't use variables.. same with coproc, exec, etc..
2020-03-03T09:14:59 #kisslinux <icyphox> dylanaraps: The link in the RSS feed 404s.
2020-03-03T09:15:04 #kisslinux <icyphox> The blog post, that is.
2020-03-03T09:15:11 #kisslinux <dylanaraps> https://k1ss.org/blog/20200303a
2020-03-03T09:15:19 #kisslinux <icyphox> It's got a trailing slash.
2020-03-03T09:28:47 #kisslinux <dylanaraps> icyphox: Fixed thanks
2020-03-03T09:31:58 #kisslinux <dylanaraps> dzove855: Do you have to open each fd?
2020-03-03T09:34:50 #kisslinux <dzove855> hmm, it depends. I do know, how do you want to keep each file open with only on fd..
2020-03-03T09:35:54 #kisslinux <icyphox> dzove855: Camel case. D:
2020-03-03T09:41:10 #kisslinux <dylanaraps> #kisslinux Hm
2020-03-03T09:41:12 #kisslinux <dylanaraps> Oops
2020-03-03T09:41:48 #kisslinux <adamantium[m]> :P
2020-03-03T09:42:07 #kisslinux <adamantium[m]> We have so many dylans in #KISS
2020-03-03T09:42:20 #kisslinux <adamantium[m]> not to mention that dilin guy
2020-03-03T09:42:41 #kisslinux <dzove855> icyphox: ? haha
2020-03-03T09:43:01 #kisslinux <adamantium[m]> icyphox:== dilin ?
2020-03-03T09:43:02 #kisslinux <dylanaraps> whatDoYouMean?
2020-03-03T09:43:28 #kisslinux <icyphox> adamantium[m]: No lol.
2020-03-03T09:43:30 #kisslinux <adamantium[m]> dylanaraps: dylan2 dylan3 dyland dilin
2020-03-03T09:43:42 #kisslinux <icyphox> I'm just icyphox. :)
2020-03-03T09:44:08 #kisslinux <dylanaraps> I am dylan2, dylan3 and dyland. ;)
2020-03-03T09:44:13 #kisslinux <adamantium[m]> hehe
2020-03-03T09:44:15 #kisslinux <dylanaraps> I'm not dilyn though
2020-03-03T09:44:19 #kisslinux <dzove855> dylanaraps: yeah, i know what camel case is, just asking on what context haha :)
2020-03-03T09:44:35 #kisslinux <dylanaraps> :P
2020-03-03T09:45:02 #kisslinux <dylanaraps> You may find this interesting dzove855: https://github.com/dylanaraps/bareutils/tree/master/bin
2020-03-03T09:45:06 #kisslinux <adamantium[m]> remove duplicate DESTDIR sorry im a dummy
2020-03-03T09:45:15 #kisslinux <dylanaraps> I never got around to tee though.
2020-03-03T09:45:30 #kisslinux <dylanaraps> Stuff like this is 10/10 https://github.com/dylanaraps/bareutils/blob/master/bin/echo
2020-03-03T09:45:39 #kisslinux <dylanaraps> > # echo in pure bash.
2020-03-03T09:45:40 #kisslinux <dylanaraps> > echo "$@"
2020-03-03T09:45:53 #kisslinux <dylanaraps> ;)
2020-03-03T09:46:49 #kisslinux <dylanaraps> The dirname/basename implementations in bareutils are wrong though.
2020-03-03T09:46:56 #kisslinux <dylanaraps> The full ones are more complex.
2020-03-03T09:47:00 #kisslinux <dylanaraps> https://github.com/dylanaraps/pure-bash-bible#get-the-directory-name-of-a-file-path
2020-03-03T09:47:07 #kisslinux <dylanaraps> https://github.com/dylanaraps/pure-bash-bible#get-the-base-name-of-a-file-path
2020-03-03T09:47:11 #kisslinux <dylanaraps> These follow POSIX
2020-03-03T09:47:13 #kisslinux <adamantium[m]> What is this bareutils
2020-03-03T09:47:23 #kisslinux <adamantium[m]> Can I swap to them with kiss a ?
2020-03-03T09:47:36 #kisslinux <dylanaraps> It's coreutils in bash
2020-03-03T09:47:39 #kisslinux <dylanaraps> Though incomplete
2020-03-03T09:48:36 #kisslinux <dylanaraps> brb in an hour or so
2020-03-03T09:48:36 #kisslinux <adamantium[m]> freaking impressive
2020-03-03T09:48:39 #kisslinux <dylanaraps> Garden time
2020-03-03T09:51:34 #kisslinux <dzove855> dylanaraps: already know i think all of your repo haha i'm inspired from some things done by you :)
2020-03-03T09:52:24 #kisslinux <dzove855> actually in tail you can add tail -f :p
2020-03-03T09:57:13 #kisslinux <dzove855> brb
2020-03-03T09:59:47 #kisslinux <dzove855> back
2020-03-03T13:52:04 #kisslinux <kiedtl> hello all
2020-03-03T13:52:48 #kisslinux <adamantium> hi kiedtl
2020-03-03T13:53:52 #kisslinux <kiedtl> anyone know if a pure POSIX sh cat is possible?
2020-03-03T13:54:11 #kisslinux <kiedtl> in bash we can do `< file` but not in posix
2020-03-03T14:01:19 #kisslinux <illiliti> read -r var < file; printf "%sn" "$var"
2020-03-03T14:05:04 #kisslinux <kiedtl> illiliti: oh nice, thanks
2020-03-03T14:10:03 #kisslinux <E5ten> That only works for one line though
2020-03-03T14:13:33 #kisslinux <dylanaraps> kiedtl: for file; do while IFS= read -r line || [ "$line" ]; do printf '%sn' "$line"; done < "$file"; done
2020-03-03T14:13:38 #kisslinux <dylanaraps> Pure sh cat
2020-03-03T14:13:45 #kisslinux <dylanaraps> So long as 'printf' is built in.
2020-03-03T14:14:06 #kisslinux <dylanaraps> Else it's not possible as there's no way to print to the screen without calling something external.
2020-03-03T14:14:12 #kisslinux <dylanaraps> (Same goes for echo)
2020-03-03T14:51:46 #kisslinux <jason> q
2020-03-03T14:51:54 #kisslinux <jason> help
2020-03-03T14:51:58 #kisslinux <jason> h
2020-03-03T14:52:18 #kisslinux <dylanaraps> Hello
2020-03-03T15:01:46 #kisslinux <sirtomato> henlo
2020-03-03T15:45:26 #kisslinux <aarng> kiedtl: https://termbin.com/ia1k
2020-03-03T16:10:13 #kisslinux <E5ten> konimex: for gtk2, what's the bmake error?
2020-03-03T16:16:13 #kisslinux <kiedtl> aarng: thanks
2020-03-03T16:19:51 #kisslinux <E5ten> konimex: and same question for libxml2?
2020-03-03T16:43:23 #kisslinux <rircEFFD2> hello
2020-03-03T16:43:54 #kisslinux <kiedtl> in the kiss repo, what are those BSD compatiblity headers for?
2020-03-03T16:44:03 #kisslinux <kiedtl> (for musl)
2020-03-03T16:44:33 #kisslinux <rircEFFD2> adamantium[m]: the package libcap seems to be wrong. stuff that should be in /usr/lib/pkgconfig is in /usr/pkgconfig
2020-03-03T17:16:00 #kisslinux <dylanaraps> kiedtl: Some packages require them and they're merely tiny headers so they're included with the musl package.
2020-03-03T19:10:39 #kisslinux <dylanaraps> Aw
2020-03-03T19:10:55 #kisslinux <dylanaraps> I slimmed down our chroot and it only shaved off 7~ MB
2020-03-03T19:22:50 #kisslinux <kiedtl> dylanaraps, where's the source for the kiss-chroot script?
2020-03-03T19:25:16 #kisslinux <kiedtl> (on github)
2020-03-03T19:25:22 #kisslinux <dylanaraps> https://github.com/kisslinux/kiss/blob/master/contrib/kiss-chroot
2020-03-03T19:26:38 #kisslinux <kiedtl> ah, thanks
2020-03-03T19:38:57 #kisslinux <dylanaraps> https://github.com/kisslinux/repo/releases/tag/1.9.9
2020-03-03T19:39:01 #kisslinux <dylanaraps> Our chroot is down to 40MB
2020-03-03T19:39:55 #kisslinux <dylanaraps> Down from 47.7MB
2020-03-03T19:53:38 #kisslinux <kiedtl> neat
2020-03-03T19:54:05 #kisslinux <kiedtl> what was done? just updating musl and other packages?
2020-03-03T19:55:48 #kisslinux <dylanaraps> I rebuilt GCC without locale support which removed 10MB of locales which weren't used anyway.
2020-03-03T19:55:54 #kisslinux <dylanaraps> I dropped perl as it's now optional.
2020-03-03T19:56:22 #kisslinux <dylanaraps> I dropped all manpages and mandoc as this should be opt-in. Curl/libressl pull down thousands of manpages too.
2020-03-03T19:56:33 #kisslinux <dylanaraps> I then updated all packages.
2020-03-03T19:57:14 #kisslinux <dylanaraps> I expected a larger decrease in size though the majority of it is binutils/gcc.
2020-03-03T19:57:25 #kisslinux <dylanaraps> We _can_ get it lower though.
2020-03-03T19:57:37 #kisslinux <dylanaraps> binutils installs a bunch of hardlinks which we could swap to symlinks.
2020-03-03T19:57:40 #kisslinux <dylanaraps> Same for 'git'
2020-03-03T19:57:48 #kisslinux <kiedtl> ah
2020-03-03T19:57:49 #kisslinux <dylanaraps> I need to investigate more
2020-03-03T19:58:38 #kisslinux <dylanaraps> Basically, '/usr' is around 180MB unpacked which is pretty much just gcc/git/binutils.
2020-03-03T19:59:54 #kisslinux <kiedtl> I'm working on a toy linux chroot/distro to see how much space is really needed for a usable setup
2020-03-03T20:00:44 #kisslinux <dylanaraps> https://termbin.com/449c
2020-03-03T20:00:52 #kisslinux <dylanaraps> That's KISS' current list for the chroot
2020-03-03T20:24:28 #kisslinux <mforney> you could probably save a bit by using bearssl instead of libressl. i recently added bearssl support to curl (available since 7.68.0)
2020-03-03T20:26:30 #kisslinux <dylanaraps> mforney: GCC + binutils make up 80% of the size I'd say (with git next in line). I think it's better to trim those 3. The user would then need to additionally install libressl later on which isn't ideal.
2020-03-03T20:27:01 #kisslinux <dylanaraps> I like that bearssl is a possibility though. I've heard good things about it.
2020-03-03T20:27:24 #kisslinux <mforney> the code is the cleanest and best documented C i've ever seen
2020-03-03T20:28:10 #kisslinux <dylanaraps> > No dynamic allocation whatsoever. There is not a single malloc() call in all the library. In fact, the whole of BearSSL requires only memcpy(), memmove(), memcmp() and strlen() from the underlying C library.
2020-03-03T20:28:20 #kisslinux <dylanaraps> This is the most interesting fact to me.
2020-03-03T20:28:44 #kisslinux <dylanaraps> Though: (On “big” systems, BearSSL will automatically use a couple more system calls to access the OS-provided clock and random number generator.
2020-03-03T20:28:47 #kisslinux <dylanaraps> Which is fair
2020-03-03T20:29:36 #kisslinux <dylanaraps> The author is also Thomas Pornin
2020-03-03T20:30:02 #kisslinux <dylanaraps> http://www.bolet.org/~pornin/cv-en.html
2020-03-03T20:31:56 #kisslinux <ioraff> dylanaraps: will the main repo's gcc _always_ be C/C++ only?
2020-03-03T20:32:16 #kisslinux <dylanaraps> ioraff: Most likely, yes.
2020-03-03T20:32:22 #kisslinux <dylanaraps> Which language were you hoping for?
2020-03-03T20:32:32 #kisslinux <dylanaraps> D? Ada?
2020-03-03T20:32:35 #kisslinux <ioraff> fortran
2020-03-03T20:32:37 #kisslinux <dylanaraps> Ah
2020-03-03T20:32:54 #kisslinux <dylanaraps> Can this not be a separate package?
2020-03-03T20:33:32 #kisslinux <dylanaraps> I'd need to know how much longer compile times will be and also the difference in package size afterwards.
2020-03-03T20:34:33 #kisslinux <dylanaraps> Does it add any dependencies?
2020-03-03T20:35:20 #kisslinux <ioraff> not entirely sure about it being a separate package. I assumed gcc required a set of common files between all of the language frontends. it does not add any dependencies.
2020-03-03T20:36:01 #kisslinux <dylanaraps> Right
2020-03-03T20:36:12 #kisslinux <dylanaraps> The first two questions stand then.
2020-03-03T20:36:13 #kisslinux <E5ten> I assume the separate package would depend on gcc so the files thing shouldn't be a problem?
2020-03-03T20:36:14 #kisslinux <kiedtl> wouldn't adding fortran support significantly increase gcc's size?
2020-03-03T20:36:28 #kisslinux <dylanaraps> kiedtl: That's what I want to know.
2020-03-03T20:36:51 #kisslinux <E5ten> dylanaraps: what factored into the nasm vs yasm choice?
2020-03-03T20:36:57 #kisslinux <ioraff> E5ten: yes, that would just create a bunch of conflicts in the alternatives system.
2020-03-03T20:37:20 #kisslinux <dylanaraps> E5ten: One less package to worry about.
2020-03-03T20:37:27 #kisslinux <ioraff> Compile times don't seem THAT much longer, but it's harder for me to tell on my ~11 year old machine.
2020-03-03T20:37:27 #kisslinux <dylanaraps> Only Firefox requires yasm now.
2020-03-03T20:37:34 #kisslinux <E5ten> ah right, what's the thing that works with nasm but not yasm again?
2020-03-03T20:37:43 #kisslinux <dylanaraps> It's just Firefox now
2020-03-03T20:37:46 #kisslinux <dylanaraps> Which requires both.
2020-03-03T20:37:56 #kisslinux <E5ten> nuts
2020-03-03T20:37:56 #kisslinux <dylanaraps> All packages which used yasm had support for nasm built in.
2020-03-03T20:38:12 #kisslinux <E5ten> yeah I just remember one thing that didn't go the other way
2020-03-03T20:38:13 #kisslinux <dylanaraps> Anything using nasm had no support for yasm though.
2020-03-03T20:38:28 #kisslinux <E5ten> what does FF need yasm for that nasm can't do?
2020-03-03T20:38:31 #kisslinux <dylanaraps> Seems nasm has more use and a more active upstream
2020-03-03T20:38:44 #kisslinux <dylanaraps> E5ten: Firefox vendors a _lot_ of crap
2020-03-03T20:38:51 #kisslinux <kiedtl> doesn't FF require both clang and gcc?
2020-03-03T20:39:00 #kisslinux <dylanaraps> kiedtl: Yes
2020-03-03T20:39:09 #kisslinux <kiedtl> lmao
2020-03-03T20:39:13 #kisslinux <dylanaraps> E5ten: Firefox's build system assumes nasm and yasm
2020-03-03T20:39:15 #kisslinux <dylanaraps> It's a mess
2020-03-03T20:39:32 #kisslinux <dylanaraps> Then there's trying to tell the underlying vendored stuff to use one or the other.
2020-03-03T20:41:09 #kisslinux <kiedtl> anyone know what's the smallest vi implementation?
2020-03-03T20:41:18 #kisslinux <kiedtl> (in terms of source size)
2020-03-03T20:41:28 #kisslinux <E5ten> can't you just like do that dumb thing a PKGBUILD we talked about here mentioned where you symlink nasm to yasm in the source dir and add that to PATH?
2020-03-03T20:41:44 #kisslinux <E5ten> or is there specific yasm stuff it uses that nasm can't do?
2020-03-03T20:42:02 #kisslinux <dylanaraps> Yup
2020-03-03T20:42:16 #kisslinux <dylanaraps> It also parses command output
2020-03-03T20:42:25 #kisslinux <dylanaraps> ie, `yasm --version`
2020-03-03T20:42:37 #kisslinux <E5ten> yikes
2020-03-03T20:42:39 #kisslinux <dylanaraps> Could be wrong about the exact flags but it does parse them.
2020-03-03T20:42:47 #kisslinux <dylanaraps> Yup
2020-03-03T20:42:54 #kisslinux <dylanaraps> Firefox makes things difficult...
2020-03-03T20:42:55 #kisslinux <E5ten> what part (like where in the source tree) is yasm used?
2020-03-03T20:43:07 #kisslinux <dylanaraps> 2 secs
2020-03-03T20:43:17 #kisslinux <dylanaraps> https://dxr.mozilla.org/mozilla-central/search?q=yasm&redirect=false
2020-03-03T20:44:16 #kisslinux <dylanaraps> There's a lot to dig through
2020-03-03T20:45:40 #kisslinux <dylanaraps> Can _maybe_ be done
2020-03-03T20:46:21 #kisslinux <E5ten> seems that the parts that use it according to https://developer.mozilla.org/en/YASM are just the jpeg and webm parts
2020-03-03T20:46:36 #kisslinux <dylanaraps> We can't use system libvpx though.
2020-03-03T20:46:38 #kisslinux <dylanaraps> It's too new.
2020-03-03T20:46:50 #kisslinux <dylanaraps> Firefox is locked to an older version which isn't compatible.
2020-03-03T20:46:57 #kisslinux <E5ten> pretty sure libwebp is the relevant part?
2020-03-03T20:47:08 #kisslinux <E5ten> or is that not used?
2020-03-03T20:47:13 #kisslinux <E5ten> I assumed that was the webm component
2020-03-03T20:47:14 #kisslinux <dylanaraps> Also in libvpx
2020-03-03T20:47:29 #kisslinux <E5ten> huh
2020-03-03T20:47:40 #kisslinux <E5ten> and libvpx can't use nasm? or specifically old libvpx can't?
2020-03-03T20:48:01 #kisslinux <dylanaraps> ooo
2020-03-03T20:48:03 #kisslinux <dylanaraps> Idea
2020-03-03T20:48:09 #kisslinux <dylanaraps> Use Firefox's vendored yasm
2020-03-03T20:48:13 #kisslinux <dylanaraps> It seems to have one
2020-03-03T20:48:23 #kisslinux <E5ten> nice
2020-03-03T20:48:42 #kisslinux <dylanaraps> I need to verify though
2020-03-03T20:51:45 #kisslinux <dylanaraps> Nothing uses yasm in community eithe.
2020-03-03T20:51:49 #kisslinux <dylanaraps> either*
2020-03-03T20:51:53 #kisslinux <dylanaraps> Literally just Firefox
2020-03-03T20:54:28 #kisslinux <dylanaraps> No vendored yasm.
2020-03-03T20:54:42 #kisslinux <E5ten> damn
2020-03-03T20:55:11 #kisslinux <dylanaraps> I'll just give it the good ol' outdated autoconf treatment.
2020-03-03T20:55:28 #kisslinux <dylanaraps> Heck, Adelie Linux do this for Python 2
2020-03-03T20:55:49 #kisslinux <E5ten> does that mean installing it in a subdir and doing some PATH fuckery?
2020-03-03T20:55:56 #kisslinux <dylanaraps> On another note: libXt is still broken in today's GCC snapshot.
2020-03-03T20:56:31 #kisslinux <dylanaraps> Just gonna set DESTDIR to '$PWD/autoconf' as it already exists.
2020-03-03T20:56:43 #kisslinux <dylanaraps> Will probably rename it to 'fake_bin' or something general.
2020-03-03T20:57:19 #kisslinux <mforney> can you patch it to use nasm instead by backporting patches from new vpx?
2020-03-03T20:57:43 #kisslinux <dylanaraps> It's not an "it's not supported in this vpx version" issue
2020-03-03T20:57:56 #kisslinux <dylanaraps> It's mozilla's build system which uses it for a myriad of things
2020-03-03T20:58:17 #kisslinux <mforney> ah
2020-03-03T20:58:33 #kisslinux <dylanaraps> It's spread across countless files too
2020-03-03T20:58:59 #kisslinux <dylanaraps> yasm hasn't been updated since it was added to KISS either.
2020-03-03T20:59:13 #kisslinux <dylanaraps> > Date: Thu Jul 18 15:08:14 2019 +0700
2020-03-03T21:04:38 #kisslinux <dylanaraps> Done
2020-03-03T21:52:56 #kisslinux <ioraff> dylanaraps: with --enable-languages=fortran, I still get "
2020-03-03T21:53:03 #kisslinux <ioraff> The following languages will be built: c,c++,fortran,lto"
2020-03-03T21:53:14 #kisslinux <ioraff> so I don't reckon it can be a separate package.
2020-03-03T21:53:42 #kisslinux <ioraff> The fortran-only files add ~30 MB
2020-03-03T21:55:29 #kisslinux <kiedtl> dylanaraps, what are your reasons for using busybox instead of sbase+ubase?
2020-03-03T21:55:51 #kisslinux <dylanaraps> ioraff: That
2020-03-03T21:56:08 #kisslinux <dylanaraps> ioraff: That's quite a lot as it'll also impact the chroot size.
2020-03-03T21:56:35 #kisslinux <dylanaraps> kiedtl: It's just the default. busybox provides a lot more utilities too.
2020-03-03T21:58:25 #kisslinux <ioraff> dylanaraps: Ah... The downside of not having split packages.
2020-03-03T21:58:32 #kisslinux <dylanaraps> Meh
2020-03-03T21:59:36 #kisslinux <dylanaraps> Nothing prevents you from having your own GCC package.
2020-03-03T21:59:45 #kisslinux <dylanaraps> You can also avoid it via a KISS hook
2020-03-03T22:01:08 #kisslinux <ioraff> I do have my own currently. It just makes my personal repo huge as I can't add my fortran-dependent packages to community.
2020-03-03T22:01:15 #kisslinux <ioraff> What would that hook look like?
2020-03-03T22:03:41 #kisslinux <E5ten> An idea for how kiss could do split packages, in the package dir have install-<split package name> and if those are present split the package into the names after the - in each of those files and if not use the build file for install instructions (how it works now)
2020-03-03T22:04:17 #kisslinux <dylanaraps> I'm not adding split packages
2020-03-03T22:04:24 #kisslinux <E5ten> Fair enough
2020-03-03T22:04:26 #kisslinux <konimex> if f18 is merged to llvm mainline things would be so much easier
2020-03-03T22:04:42 #kisslinux <E5ten> I thought that happened already?
2020-03-03T22:04:48 #kisslinux <E5ten> I guess not
2020-03-03T22:04:50 #kisslinux <konimex> not as of llvm10
2020-03-03T22:05:28 #kisslinux <E5ten> Ah, what about master (too lazy to check cuz mobile)
2020-03-03T22:06:26 #kisslinux <konimex> let me check
2020-03-03T22:06:53 #kisslinux <konimex> nope, not yet
2020-03-03T22:07:17 #kisslinux <dylanaraps> ioraff: It seems that a hook won't work for GCC in this case.
2020-03-03T22:07:21 #kisslinux <E5ten> Rip, I wonder if it'll make it before 11
2020-03-03T22:07:51 #kisslinux <dylanaraps> I really don't see the problem in having your own GCC package.
2020-03-03T22:07:59 #kisslinux <konimex> the best case for gcc is to symlink everything but build
2020-03-03T22:08:48 #kisslinux <dylanaraps> There's no difference in a package being in community or your own repository
2020-03-03T22:08:58 #kisslinux <dylanaraps> You maintain it either way
2020-03-03T22:09:09 #kisslinux <ioraff> repology
2020-03-03T22:09:14 #kisslinux <dylanaraps> Others users can enable your repository as well
2020-03-03T22:09:30 #kisslinux <dylanaraps> Sure
2020-03-03T22:09:53 #kisslinux <dylanaraps> That's minor though
2020-03-03T22:18:35 #kisslinux <ioraff> very convenient if a package doesn't have its own release feed. one of the main reasons I've even added stuff I've packaged to community.
2020-03-03T22:19:44 #kisslinux <dylanaraps> I have a solution for you.
2020-03-03T22:20:27 #kisslinux <ioraff> do tell
2020-03-03T22:22:49 #kisslinux <dzove855> dylanaraps: did you start already of writing fold in pure bash?
2020-03-03T22:25:17 #kisslinux <dylanaraps> dzove855: Yes
2020-03-03T22:25:19 #kisslinux <dylanaraps> It's very slow
2020-03-03T22:27:26 #kisslinux <dzove855> sahre it if you want, i'm interested to learn how does all the design stuf works (resize etc.. i'm really bad in those kind of things)
2020-03-03T22:27:48 #kisslinux <dzove855> s/sahre/share
2020-03-03T22:40:29 #kisslinux <dylanaraps> ioraff: https://termbin.com/q56cx
2020-03-03T22:40:30 #kisslinux <dylanaraps> Enjoy
2020-03-03T22:41:14 #kisslinux <dylanaraps> What it looks like: https://termbin.com/rwyq
2020-03-03T22:43:36 #kisslinux <dylanaraps> dzove855: I need to find it. It's either in a dir somewhere or in the git stash
2020-03-03T22:43:51 #kisslinux <dylanaraps> I've written 5-6 different ones
2020-03-03T22:44:02 #kisslinux <dylanaraps> All slow
2020-03-03T22:44:12 #kisslinux <ioraff> dylanaraps: very nice. Thanks much.
2020-03-03T22:45:10 #kisslinux <dylanaraps> ioraff: I'll add this as 'kiss-outdated'
2020-03-03T22:45:49 #kisslinux <ioraff> just added it to my script dir with that exact name
2020-03-03T22:46:05 #kisslinux <dylanaraps> ;)
2020-03-03T22:46:31 #kisslinux <dylanaraps> I'll also add support for specifying a list
2020-03-03T22:49:15 #kisslinux <dylanaraps> Pushed
2020-03-03T22:50:09 #kisslinux <konimex> speaking of firefox, next ESR should be on 76, right?
2020-03-03T22:50:41 #kisslinux <dylanaraps> 78 iirc
2020-03-03T22:50:54 #kisslinux <dylanaraps> > Firefox 78.3
2020-03-03T22:50:56 #kisslinux <dylanaraps> Yup
2020-03-03T22:51:05 #kisslinux <dylanaraps> Specifically: Firefox 68.10; 78.0
2020-03-03T22:51:21 #kisslinux <dylanaraps> Release date: 2020-06-30
2020-03-03T22:51:25 #kisslinux <dylanaraps> https://wiki.mozilla.org/Release_Management/Calendar
2020-03-03T22:51:41 #kisslinux <konimex> huh, I thought ESR was between 8 versions since last was 60, changing the release schemes again eh
2020-03-03T22:51:56 #kisslinux <dylanaraps> They changed to a monthly schedule
2020-03-03T22:51:59 #kisslinux <dylanaraps> Instead of 6 weeks
2020-03-03T22:52:04 #kisslinux <dylanaraps> > Four week schedule starting late 2019.
2020-03-03T22:52:09 #kisslinux <dylanaraps> Right at the bottom
2020-03-03T22:55:30 #kisslinux <dylanaraps> We need a browser for later on when Firefox drops Xorg though
2020-03-03T22:55:52 #kisslinux <dylanaraps> Same goes for ALSA when pipewire becomes mainstream
2020-03-03T22:56:20 #kisslinux <dylanaraps> Also if dbus becomes impossible to remove...
2020-03-03T22:56:24 #kisslinux <dylanaraps> Fun days ahead
2020-03-03T22:59:11 #kisslinux <konimex> yeah let's hope wayland becomes the next GNU Hurd
2020-03-03T23:00:23 #kisslinux <dzove855> hmm create a wayland alternative, which just provides the same function like wayland but behind xorg :D
2020-03-03T23:00:45 #kisslinux <dzove855> a wrapper for xorg
2020-03-03T23:03:00 #kisslinux <kiedtl> Firefox is going to drop Xorg?
2020-03-03T23:03:01 #kisslinux <mforney> i think it would actually be pretty easy to make a "waylandx" (opposite of xwayland) that just forwards buffers to x11 via the shm and dri3 extensions
2020-03-03T23:03:40 #kisslinux <dylanaraps> kiedtl: Of course.
2020-03-03T23:04:13 #kisslinux <dylanaraps> Xorg has a maximum of 9-10 years left if Wayland becomes mainstream in that time.
2020-03-03T23:04:48 #kisslinux <dylanaraps> Red Hat have Xorg on life support today with the intention of letting it die once RHEL _whatever_ is released.
2020-03-03T23:04:54 #kisslinux <dylanaraps> Hence the 9-10 years.
2020-03-03T23:05:30 #kisslinux <dylanaraps> > Once we are done with this we expect X.org to go into hard maintenance mode fairly quickly. The reality is that X.org is basically maintained by us and thus once we stop paying attention to it there is unlikely to be any major new releases coming out and there might even be some bitrot setting in over time. We will keep an eye on it as we will want to ensure X.org stays supportable until the end of the RHEL8 lifecycle at a
2020-03-03T23:05:34 #kisslinux <dylanaraps> https://blogs.gnome.org/uraeus/2019/06/24/on-the-road-to-fedora-workstation-31/
2020-03-03T23:06:31 #kisslinux <kiedtl> Oh god
2020-03-03T23:06:33 #kisslinux <kiedtl> wayland sucks
2020-03-03T23:06:37 #kisslinux <dylanaraps> Firefox's Linux support is largely maintained by an employee of Red Hat as well.
2020-03-03T23:06:53 #kisslinux <dylanaraps> He implemented VAAPI support for Wayland just now
2020-03-03T23:07:12 #kisslinux <dylanaraps> https://bugzilla.mozilla.org/show_bug.cgi?id=1610199#c31
2020-03-03T23:07:53 #kisslinux <dylanaraps> He's leading the Wayland port as well
2020-03-03T23:08:49 #kisslinux <dylanaraps> Lots to read here: https://mastransky.wordpress.com/
2020-03-03T23:12:23 #kisslinux <konimex> well if Xorg is dropped then what would you do? keep using it?
2020-03-03T23:12:32 #kisslinux <dylanaraps> The start of it is here: https://bugzilla.mozilla.org/show_bug.cgi?id=1579352
2020-03-03T23:12:36 #kisslinux <dylanaraps> >
2020-03-03T23:12:40 #kisslinux <dylanaraps> >
2020-03-03T23:12:54 #kisslinux <dylanaraps> > Compile with/without X11 support
2020-03-03T23:13:21 #kisslinux <dylanaraps> konimex: A lot can happen in 10 years
2020-03-03T23:13:37 #kisslinux <dylanaraps> I was 12 years old 10 years ago.
2020-03-03T23:13:41 #kisslinux <dylanaraps> ;)
2020-03-03T23:13:49 #kisslinux <kiedtl> One thing I especially hate about wayland is that the compositor is the window manager
2020-03-03T23:14:00 #kisslinux <kiedtl> the window manager should be the window manager
2020-03-03T23:14:03 #kisslinux <dylanaraps> The compositor is the everything
2020-03-03T23:14:11 #kisslinux <dylanaraps> It's the display server as well
2020-03-03T23:14:15 #kisslinux <dylanaraps> And the hotkey manager
2020-03-03T23:14:16 #kisslinux <kiedtl> yes
2020-03-03T23:14:22 #kisslinux <konimex> it's a matter of workflow for me but sxhkd and bspwm are both killers
2020-03-03T23:14:32 #kisslinux <konimex> i3 (and sway) sucks
2020-03-03T23:14:41 #kisslinux <kiedtl> Which makes it extremely difficult to develop a wm for wayland
2020-03-03T23:14:43 #kisslinux <dylanaraps> All with its own protocols which aren't portable across other wayland implementations
2020-03-03T23:15:16 #kisslinux <dylanaraps> Recent example. OBS has wayland support for GNOME via a plugin and wlroots via a plugin.
2020-03-03T23:15:21 #kisslinux <konimex> you should invite back that wayland evangelist back in discord to argue about that
2020-03-03T23:15:24 #kisslinux <dylanaraps> I'm sure a KDE plugin will follow.
2020-03-03T23:15:36 #kisslinux <dzove855> that's pretty the case for a lot of new things comming..
2020-03-03T23:15:50 #kisslinux <illiliti> xorg clutter your ~/ !
2020-03-03T23:16:06 #kisslinux <dylanaraps> I'm not swapping to Wayland to free up some files in ~
2020-03-03T23:16:07 #kisslinux <dylanaraps> lol
2020-03-03T23:16:16 #kisslinux <dzove855> they're trying to make everything more "user friendly"
2020-03-03T23:16:33 #kisslinux <dylanaraps> Besides: -> ls -1 ~ | wc -l --> 471
2020-03-03T23:17:05 #kisslinux <dzove855> dylanaraps: how is that even possible? 471?? haha
2020-03-03T23:17:43 #kisslinux <dylanaraps> There's order in chaos
2020-03-03T23:17:53 #kisslinux <dzove855> haha i'm about 31
2020-03-03T23:18:36 #kisslinux <dylanaraps> Wayland is just a protocol so it can do no wrong
2020-03-03T23:18:38 #kisslinux <dylanaraps> Remember this
2020-03-03T23:19:51 #kisslinux <dylanaraps> Everything beyond pushing pixels to the screen is a protocol extension
2020-03-03T23:19:58 #kisslinux <dylanaraps> (Has this changed recently(?))
2020-03-03T23:21:17 #kisslinux <dylanaraps> https://gitlab.freedesktop.org/wayland/wayland-protocols/-/blob/master/stable/xdg-shell/xdg-shell.xml#L34
2020-03-03T23:21:20 #kisslinux <dylanaraps> Huzzah?
2020-03-03T23:22:25 #kisslinux <dylanaraps> > wayland-protocols contains Wayland protocols that add functionality not available in the Wayland core protocol.
2020-03-03T23:22:27 #kisslinux <dylanaraps> Oh
2020-03-03T23:22:30 #kisslinux <dylanaraps> It is an extension
2020-03-03T23:22:45 #kisslinux <dylanaraps> Just a "standardized" one
2020-03-03T23:24:32 #kisslinux <konimex> https://danluu.com/cli-complexity/
2020-03-03T23:24:40 #kisslinux <mforney> well, don't you rely on plenty of standardized x11 protocols?
2020-03-03T23:24:47 #kisslinux <dylanaraps> Yes
2020-03-03T23:25:28 #kisslinux <dylanaraps> This is still an issue in Wayland though. There are too many non-standard protocols for what I'd call essential functionality.
2020-03-03T23:25:40 #kisslinux <E5ten> dylanaraps: I think I've changed my mind and will switch to libressl, and the convincing factor is that it has cmake lol
2020-03-03T23:25:52 #kisslinux <dylanaraps> Which reduces portability between wayland implementations.
2020-03-03T23:26:14 #kisslinux <dilyn> Lol wtf tar calm down with those options
2020-03-03T23:26:24 #kisslinux <dylanaraps> E5ten: Nice. I don't think many patches are needed (if any) nowadays.
2020-03-03T23:26:42 #kisslinux <mforney> yes, i agree that fragmantation between wayland implementations is an issue. if there were multiple commonly used x11 implementations, i think it'd be an issue there as well
2020-03-03T23:27:09 #kisslinux <illiliti_> xorg have similar 'bloatware' https://en.wikipedia.org/wiki/XFixes
2020-03-03T23:27:24 #kisslinux <dylanaraps> That's exactly it. We're all using a single implementation of X11.
2020-03-03T23:29:51 #kisslinux <dylanaraps> The core wayland protocol is too bare. Were it more complete and were it to include what I'd call essential functonality from day 1, we wouldn't be in this situation.
2020-03-03T23:33:26 #kisslinux <illiliti_> wayland main problem is nvidia
2020-03-03T23:33:41 #kisslinux <illiliti_> https://github.com/swaywm/sway/issues/490
2020-03-03T23:34:07 #kisslinux <konimex> what nvidia wayland about on gnome and kde?
2020-03-03T23:34:57 #kisslinux <konimex> as ddevault is certainly hostile to it
2020-03-03T23:35:19 #kisslinux <dylanaraps> I wouldn't call this a problem on NVIDIA's side of the fence either. If you're aiming to replace Xorg, you need to support all hardware. The reality is that NVIDIA use GBM. Deal with it.
2020-03-03T23:35:48 #kisslinux <dylanaraps> Or was it EGLStreams? I forget
2020-03-03T23:36:21 #kisslinux <dylanaraps> It is EGLStreams
2020-03-03T23:36:37 #kisslinux <dylanaraps> Sway actually had NVIDIA support a long while ago.
2020-03-03T23:37:17 #kisslinux <konimex> so it was actively removed in spite?
2020-03-03T23:37:21 #kisslinux <konimex> not familiar with it
2020-03-03T23:38:04 #kisslinux <dylanaraps> https://github.com/Cloudef/wlc/commit/1364e92c251bf300c6245ebfca635c9308d25df9
2020-03-03T23:38:12 #kisslinux <dylanaraps> iirc sway used to use wlc
2020-03-03T23:38:41 #kisslinux <dylanaraps> Yup: https://drewdevault.com/2018/05/27/Why-rewrite-wlc.html
2020-03-03T23:42:26 #kisslinux <illiliti_> eglstreams is shit which works only on nvidia proprietary driver. support eglstreams is a pain in the ass
2020-03-03T23:43:14 #kisslinux <dylanaraps> Yes. If you're going to _replace_ Xorg you need to support everything though.
2020-03-03T23:44:12 #kisslinux <dylanaraps> s/If/But, if/
2020-03-03T23:44:47 #kisslinux <konimex> you know, I've been thinking, why in some packages you need to define MKDIR_P="install -d" ? difference between coreutils and busybox?
2020-03-03T23:45:06 #kisslinux <dylanaraps> konimex: Good question
2020-03-03T23:45:31 #kisslinux <dylanaraps> It's only in e2fsprogs in the official repositories
2020-03-03T23:46:36 #kisslinux <dylanaraps> > make[1]: config/install-sh: No such file or directory
2020-03-03T23:46:57 #kisslinux <mforney> nvidia (and everyone else) seems on board with drm format modifiers, so i think things will get better in the future
2020-03-03T23:47:14 #kisslinux <dylanaraps> > MKDIR_P = config/install-sh -c -d
2020-03-03T23:47:24 #kisslinux <dylanaraps> It ends up being this.
2020-03-03T23:47:38 #kisslinux <dylanaraps> -c Just copy (default)
2020-03-03T23:47:42 #kisslinux <dylanaraps> -d Create directories
2020-03-03T23:48:22 #kisslinux <konimex> DRM as in direct rendering manager or...
2020-03-03T23:48:29 #kisslinux <mforney> yes
2020-03-03T23:50:17 #kisslinux <dylanaraps> -> grep -r MKDIR_P . | wc -l
2020-03-03T23:50:18 #kisslinux <dylanaraps> 114
2020-03-03T23:50:23 #kisslinux <dylanaraps> Best we not touch this one
2020-03-03T23:53:47 #kisslinux <dylanaraps> > $as_echo_n "checking for a thread-safe mkdir -p... " >&6; }
2020-03-03T23:53:55 #kisslinux <dylanaraps> Unless our mkdir isn't thread safe(?)
2020-03-03T23:54:42 #kisslinux <dylanaraps> Oh
2020-03-03T23:54:53 #kisslinux <dylanaraps> The configure script hardcodes 'mkdir --version'
2020-03-03T23:55:07 #kisslinux <dylanaraps> > for ac_prog in mkdir gmkdir; do
2020-03-03T23:55:14 #kisslinux <dylanaraps> > case `"$as_dir/$ac_prog$ac_exec_ext" --version 2>&1` in #(
2020-03-03T23:55:25 #kisslinux <dylanaraps> > 'mkdir (GNU coreutils) '* | 2020-03-03T23:55:28 #kisslinux <dylanaraps> > 'mkdir (coreutils) '* | 2020-03-03T23:55:31 #kisslinux <dylanaraps> > 'mkdir (fileutils) '4.1*)