💾 Archived View for gemini.ctrl-c.club › ~phoebos › logs › freenode-kisslinux-2020-05-12.txt captured on 2024-05-26 at 16:25:11.
⬅️ Previous capture (2021-12-17)
-=-=-=-=-=-=-
2020-05-12T00:18:07 #kisslinux <nerditup> E5ten: I noticed that yesterday as well when I was going through it
2020-05-12T00:18:32 #kisslinux <nerditup> There's a few nits I'll submit a PR for
2020-05-12T00:27:34 #kisslinux <ominous_anonymou> @onodera it depends, i think pipewire could be a good thing as audio on linux can be quite annoying. however, i'm also not a fan of making yet another thing that breaks previous configurations and applications (cue https://xkcd.com/927/)
2020-05-12T00:34:23 #kisslinux <ominous_anonymou> that being said i haven't looked at pipewire at all so i don't know
2020-05-12T00:37:51 #kisslinux <himmalerin> I was mildly excited for pipewire but since getting into Kiss I've been trying to simplify my software, dbus dependency sucks
2020-05-12T00:40:34 #kisslinux <ominous_anonymou> yep agreed. you basically can't do bluetooth without dbus, either
2020-05-12T01:02:19 #kisslinux <himmalerin> I love the convenience of totally avoiding cords but then you lose convenience on the software side
2020-05-12T01:02:24 #kisslinux <himmalerin> tradeoffs all around
2020-05-12T05:44:42 #kisslinux <dylan03> kisslinuxuser: What is that output from? I cant reproduce at all.
2020-05-12T05:45:20 #kisslinux <kisslinuxuser> dylan03: happens all the time when im trying to install a package :/
2020-05-12T05:46:02 #kisslinux <kisslinuxuser> its a fresh install
2020-05-12T05:47:53 #kisslinux <dylan03> Output of 'ls -1 /root/.cacke/kiss' ?
2020-05-12T05:53:28 #kisslinux <kisslinuxuser> dylan03: 'ls -1 /root/.cache/kiss bin logs sources .. there is nothing in logs either
2020-05-12T05:55:42 #kisslinux <kisslinuxuser> dylan03: just tried to compile alsa-utils
2020-05-12T05:55:48 #kisslinux <kisslinuxuser> Run 'kiss i alsa-utils' to install the package(s)rm: can't remove '/root/.cache/kiss/build-351/alsa-utils/axfer': Directory not empty
2020-05-12T05:56:15 #kisslinux <kisslinuxuser> basically same error as before
2020-05-12T05:59:58 #kisslinux <dylan03> 'ls -ld /root/.cache/kiss'?
2020-05-12T06:00:04 #kisslinux <dylan03> I can't reproduce this at all.
2020-05-12T06:02:18 #kisslinux <dylan03> Also, I don't know where those errors are coming from either.
2020-05-12T06:02:24 #kisslinux <dylan03> Do you have $KISS_HOOK set?
2020-05-12T06:04:07 #kisslinux <kisslinuxuser> dylan03: drwxr-xr-x 6 root root 61 May 12 09:54 /root/.cache/kiss
2020-05-12T06:04:14 #kisslinux <kisslinuxuser> seems like the folder/s doesnt get deleted for some reason
2020-05-12T06:04:37 #kisslinux <kisslinuxuser> ls /root/.cache/kiss/build-351/alsa-utils/axfer/xfer-libasound-irq-rw.o
2020-05-12T06:05:48 #kisslinux <kisslinuxuser> its also not on every package.. which is even more weird
2020-05-12T06:06:45 #kisslinux <kisslinuxuser> dylan03: is $KISS-HOOK default? didn't changed anything at all besides adding the community repo
2020-05-12T06:06:52 #kisslinux <dylan03> It's not default
2020-05-12T06:07:32 #kisslinux <dylan03> Tried 'rm -rf /root/.cache/kiss/build-* /root/.cache/kiss/extract-* /root/.cache/kiss/pkg-*'?
2020-05-12T06:10:26 #kisslinux <kisslinuxuser> dylan03: did that just now and tried to install another package
2020-05-12T06:10:28 #kisslinux <kisslinuxuser> but still the same error
2020-05-12T06:10:40 #kisslinux <kisslinuxuser> Run 'kiss i wpa_supplicant' to install the package(s) rm: can't remove '/root/.cache/kiss/build-1016/wpa_supplicant/src/drivers'
2020-05-12T06:10:51 #kisslinux <kisslinuxuser> rm: can't remove '/root/.cache/kiss/build-1016/wpa_supplicant/src/utils': Directory not empty
2020-05-12T06:14:02 #kisslinux <dylan03> Output of 'kiss v'?
2020-05-12T06:14:33 #kisslinux <dylan03> Also, how are you running 'kiss'? As which user? etc
2020-05-12T06:14:48 #kisslinux <dylan03> You shouldn't be doing 'sudo kiss' or 'doas kiss' fyi.
2020-05-12T06:15:57 #kisslinux <kisslinuxuser> dylan03: just "su" then entering password, then "kiss b package"
2020-05-12T06:15:59 #kisslinux <kisslinuxuser> sec getting kiss v
2020-05-12T06:17:14 #kisslinux <dylan03> 'kiss' can be run as a normal user as well.
2020-05-12T06:17:26 #kisslinux <dylan03> I really don't know where these errors are coming from.
2020-05-12T06:17:46 #kisslinux <kisslinuxuser> dylan03: 1.13.5
2020-05-12T06:18:10 #kisslinux <dylan03> The only 'rm' which could cause this is: rm -rf -- "$@"
2020-05-12T06:18:17 #kisslinux <dylan03> (In pkg_clean())
2020-05-12T06:18:21 #kisslinux <dylan03> You can try commenting it out.
2020-05-12T06:18:36 #kisslinux <dylan03> Just 'vim /usr/bin/kiss', find 'pkg_clean()' and comment that line.
2020-05-12T06:21:29 #kisslinux <kisslinuxuser> dylan03: that did the fix
2020-05-12T06:21:31 #kisslinux <kisslinuxuser> thanks!
2020-05-12T06:22:00 #kisslinux <dylan03> Do the directories in the error messages exist?
2020-05-12T06:23:07 #kisslinux <kisslinuxuser> dylan03: yeah
2020-05-12T06:23:26 #kisslinux <kisslinuxuser> for example '/root/.cache/kiss/build-351/alsa-utils/axfer' did
2020-05-12T06:23:37 #kisslinux <kisslinuxuser> and wasn't empty, so it didnt got deleted
2020-05-12T06:25:20 #kisslinux <dylan03> The 'rm' has '-rf' attached and you're running as 'root'. It should never fail.
2020-05-12T06:25:28 #kisslinux <dylan03> This is why I find it odd.
2020-05-12T06:29:53 #kisslinux <dylan03> Does running 'kiss b <pkg>' as a normal user cause the issue?
2020-05-12T06:35:07 #kisslinux <kisslinuxuser> dylan03: yeah
2020-05-12T06:35:09 #kisslinux <kisslinuxuser> directory not empty too
2020-05-12T06:36:13 #kisslinux <dylan03> That's very odd.
2020-05-12T06:36:32 #kisslinux <dylan03> Example: 'rm -rf alsdjladjlasdj'
2020-05-12T06:36:46 #kisslinux <dylan03> This file does not exist though 'rm' will display no messages about it.
2020-05-12T06:37:00 #kisslinux <dylan03> Same goes with 'rm -rf djladjlad/' for a directory.
2020-05-12T06:37:16 #kisslinux <dylan03> In other words, it should only fail for permissions issues.
2020-05-12T06:38:05 #kisslinux <dylan03> 'ls -l /root/.cache/kiss' ?
2020-05-12T06:38:14 #kisslinux <dylan03> (It's an 'L')
2020-05-12T06:44:43 #kisslinux <kisslinuxuser> dylan03: https://pastebin.com/raw/pBEvt63W
2020-05-12T06:45:36 #kisslinux <dylan03> OK
2020-05-12T06:45:43 #kisslinux <kisslinuxuser> dylan03: dunno if that helps at all but doing rm -rf via commandline worked without a error message
2020-05-12T06:45:47 #kisslinux <dylan03> I've pushed a fix.
2020-05-12T06:46:05 #kisslinux <dylan03> Forcing the 'rm' to be silent basically.
2020-05-12T06:46:17 #kisslinux <dylan03> As the files are being removed anyway.]
2020-05-12T06:51:00 #kisslinux <kisslinuxuser> dylan03: hm could it be the problem that im not using ext4?
2020-05-12T06:51:02 #kisslinux <kisslinuxuser> using XFS atm
2020-05-12T06:54:16 #kisslinux <dylan03> I have no idea. Anyway. I'll release a new version of the package manager shortly and we'll see how the fix goes.
2020-05-12T06:54:58 #kisslinux <kisslinuxuser> dylan03: tested the fix manually, it works :D
2020-05-12T06:55:06 #kisslinux <kisslinuxuser> But the folders doesn't get deleted, should that be an issue?
2020-05-12T06:56:52 #kisslinux <dylan03> kisslinuxuser: Yeah. That's an issue. What happens if you manually remove them with 'rm'?
2020-05-12T06:57:38 #kisslinux <kisslinuxuser> dylan03: that works fine, no errors at all.
2020-05-12T07:00:34 #kisslinux <dylan03> kisslinuxuser: I've pushed another commit which may fix the issue.
2020-05-12T07:01:06 #kisslinux <dylan03> https://termbin.com/mwy2
2020-05-12T07:01:17 #kisslinux <dylan03> Replace your pkg_clean() with this one and let me know how it goes.
2020-05-12T07:07:56 #kisslinux <kisslinuxuser> wooops
2020-05-12T07:08:02 #kisslinux <kisslinuxuser> dylan02: still same, build folder still exists
2020-05-12T07:08:24 #kisslinux <dylan02> It's really odd that the 'rm' is failing from inside the package manager.
2020-05-12T07:09:22 #kisslinux <dylan02> (But it works outside of it)
2020-05-12T07:11:17 #kisslinux <dylan02> You're using busybox I presume (You haven't changed coreutils)?
2020-05-12T07:12:27 #kisslinux <kisslinuxuser> dylan02: yeah using busybox
2020-05-12T07:12:29 #kisslinux <kisslinuxuser> the only problem i could think of would be XFS
2020-05-12T07:14:07 #kisslinux <dylan02> https://superuser.com/questions/769902/rm-rf-cannot-remove-some-folders-on-xfs-system
2020-05-12T07:14:10 #kisslinux <dylan02> Maybe related?
2020-05-12T07:14:45 #kisslinux <dylan02> Also this: https://github.com/moby/moby/issues/27358
2020-05-12T07:15:32 #kisslinux <dylan02> It does seem to be an XFS error
2020-05-12T07:16:03 #kisslinux <kisslinuxuser> dylan02: hm should i just reinstall with ext4 and see if that error still exists?
2020-05-12T07:18:01 #kisslinux <dylan02> Tried xfs_repair?
2020-05-12T07:24:48 #kisslinux <kisslinuxuser> dylan02: xfsprogs build failed https://termbin.com/y7ko
2020-05-12T07:29:19 #kisslinux <dylan02> It builds fine here.
2020-05-12T07:29:22 #kisslinux <dylan02> Can anyone else reproduce?
2020-05-12T08:14:33 #kisslinux <dylan02> In the next version of KISS you'll be able to use it rootless via $KISS_PATH.
2020-05-12T08:15:06 #kisslinux <dylan02> Just set 'KISS_PATH=~/dir' and everything will be contained to ~/dir (minus kiss cache directory which retains host).
2020-05-12T08:15:32 #kisslinux <dylan02> Example: SS_PATH=~/dir kiss i baselayout
2020-05-12T08:15:36 #kisslinux <dylan02> KISS_PATH*
2020-05-12T08:37:55 #kisslinux <dylan02> https://github.com/kisslinux/kiss/commit/d91820834a1e6ad312313c85b2060e0090e284b1
2020-05-12T08:38:15 #kisslinux <dylan02> The package manager will now log post-install output (as well as display it all at once at the end).
2020-05-12T09:50:35 #kisslinux <mattx433> hello
2020-05-12T09:51:09 #kisslinux <mattx433> jedavies: llvm finally built, but now mtdev has a missing dependency on autoreconf
2020-05-12T10:11:59 #kisslinux <mattx433> correction, missing dependencies on autoconf and automake
2020-05-12T10:12:31 #kisslinux <mattx433> and libtool
2020-05-12T10:19:17 #kisslinux <mattx433> alright, xorg-server is building. apparently Mesa built itself with panfrost for Mali and rockchip graphics too.
2020-05-12T10:21:24 #kisslinux <mattx433> hooray o/ it has built
2020-05-12T10:31:19 #kisslinux <mattx433> jedavies: success, I have xorg working with kiss-aarch64 on a Rock Pi 4.
2020-05-12T11:19:12 #kisslinux <mattx433> obligatory neofetch at https://mattx.info.tm/rockpi4screenshot.png
2020-05-12T12:09:38 #kisslinux <ominous_anonymou> that's awesome, @mattx433!
2020-05-12T14:18:45 #kisslinux <ominous_anonymou> is there a recommendation for xdummy over xvfb, or maybe an alternative to those two?
2020-05-12T14:19:38 #kisslinux <ominous_anonymou> i'd like to look into getting xpra set up on kiss
2020-05-12T14:19:54 #kisslinux <ominous_anonymou> but not need a display connected
2020-05-12T14:46:46 #kisslinux <perish> Hm
2020-05-12T14:47:13 #kisslinux <perish> I've got a package that succeeds to patch with `patch` from community but not with busybox
2020-05-12T15:13:03 #kisslinux <perish> Mousepad, XFCE4-terminal and dependencies have been added to kiss-xfce4
2020-05-12T15:32:24 #kisslinux <claudia02> dilynm: how is packaging kde framework going?
2020-05-12T15:33:21 #kisslinux <dilynm> Stalled hard
2020-05-12T15:33:35 #kisslinux <perish> Ouch
2020-05-12T15:33:41 #kisslinux <perish> What problem?
2020-05-12T15:33:57 #kisslinux <dilynm> Unrelated to the kde stuff directly, thankfully(?)
2020-05-12T15:34:08 #kisslinux <dilynm> Qt5-webengine returns a strange error when building it
2020-05-12T15:34:21 #kisslinux <dilynm> Perhaps unrelated, the kernel also returns a make error
2020-05-12T15:34:23 #kisslinux <perish> I'd say thankfully
2020-05-12T15:34:36 #kisslinux <perish> I'm finally testing out all my packages on real hardware today
2020-05-12T15:34:48 #kisslinux <dilynm> Tried all sorts of things; now I'm building gcc again to see if that fixes it, otherwise I'm lost
2020-05-12T15:34:53 #kisslinux <claudia02> :2020-05-12T15:34:54 #kisslinux <dilynm> That's exciting!
2020-05-12T15:35:00 #kisslinux <perish> Aye
2020-05-12T15:35:13 #kisslinux <perish> On my big, clunky old laptop
2020-05-12T15:35:18 #kisslinux <perish> I can't even type on it anymore
2020-05-12T15:35:26 #kisslinux <perish> I'm too used to my new one's layout
2020-05-12T15:35:49 #kisslinux <perish> It's funny how quickly 4 years of muscle memory can unlearn itself
2020-05-12T15:36:18 #kisslinux <dilynm> I feel that
2020-05-12T15:36:32 #kisslinux <dilynm> I've been using the same laptop for six years. Every other laptop feels completely alien
2020-05-12T15:36:44 #kisslinux <perish> Fair
2020-05-12T15:36:52 #kisslinux <perish> I've gone from a 14 inch to an 11 inch laptop
2020-05-12T15:37:03 #kisslinux <perish> Now I can actually use it on my lap
2020-05-12T15:37:03 #kisslinux <dilynm> Ew
2020-05-12T15:37:10 #kisslinux <perish> Hey, small laptops are nice
2020-05-12T15:37:20 #kisslinux <perish> The other one is heavy and large
2020-05-12T15:37:28 #kisslinux <perish> Great machine, served me well
2020-05-12T15:37:44 #kisslinux <dilynm> Fair enough
2020-05-12T16:05:33 #kisslinux <perish> dylan02, Regarding your comment, would the way to remove intltool and gettext be the 'texinfo' method?
2020-05-12T16:05:53 #kisslinux <perish> Creating a shell script that outputs the version, that is
2020-05-12T16:14:11 #kisslinux <dilynm> Alright. The kernel issue is related to a version, not the kernel in generally I can fix that.
2020-05-12T16:14:19 #kisslinux <dilynm> The webengine issue does not CARE ONE LICK
2020-05-12T16:14:33 #kisslinux <dilynm> Log, for anyone who has a clue: ix.io/2lOg
2020-05-12T16:15:54 #kisslinux <dilynm> The only instance of error is about uint32_t being undeclared
2020-05-12T16:16:11 #kisslinux <perish> Ouch
2020-05-12T16:17:27 #kisslinux <dilynm> Yeah. Nothing seems wrong with /usr/include/stdint.h
2020-05-12T16:21:23 #kisslinux <himmalerin> dylan02: when copying folders in build files should I use `install -t` or `cp` with -a or -r?
2020-05-12T16:29:58 #kisslinux <jedavies> mattx443: good stuff! Will check the mtdev deps
2020-05-12T16:43:12 #kisslinux <dilynm> SOB...
2020-05-12T16:43:28 #kisslinux <dilynm> looks like webengine issues are gcc 10 related. Gcc 9.2 is building it so far with no issue
2020-05-12T16:43:54 #kisslinux <dilynm> Anyone on gcc 10 care to confirm? Build should fail in less than 20 minutes or so
2020-05-12T16:44:55 #kisslinux <himmalerin> sure, where's the repository?
2020-05-12T16:45:50 #kisslinux <dilynm> It's in community
2020-05-12T16:45:55 #kisslinux <dilynm> Just qt5-webengine
2020-05-12T16:46:00 #kisslinux <dilynm> Although it does require qt5
2020-05-12T16:46:47 #kisslinux <himmalerin> oh alright! Build has been started, though there are some dependencies that need to be built first
2020-05-12T16:50:48 #kisslinux <dilynm> The issue might just be really dumb? But there's no #include <stdint.h> in one of the header files (namely, the one specified in the error message).
2020-05-12T16:50:53 #kisslinux <dilynm> So... Um
2020-05-12T16:51:16 #kisslinux <perish> Ouch
2020-05-12T16:53:29 #kisslinux <dilynm> Looks like if I add it to a single file it should fix the problem™️
2020-05-12T16:55:02 #kisslinux <himmalerin> ouch indeed. Why would it build under gcc 9.2 though?
2020-05-12T16:57:50 #kisslinux <dilynm> Because God is a trickster
2020-05-12T16:58:14 #kisslinux <himmalerin> fair enough :P
2020-05-12T16:58:18 #kisslinux <himmalerin> can confirm it fails though
2020-05-12T16:58:58 #kisslinux <himmalerin> actually building qt5 failed, not building the webengine
2020-05-12T17:00:54 #kisslinux <dilynm> Oh? What's the error there
2020-05-12T17:02:37 #kisslinux <himmalerin> I don't actually see the error, just that there was one http://0x0.st/i_7w.txt
2020-05-12T17:04:49 #kisslinux <dilynm> File '***************' not valid
2020-05-12T17:04:53 #kisslinux <dilynm> No shit, gmake
2020-05-12T17:05:07 #kisslinux <dilynm> That's a 'known' issue, unfortunately
2020-05-12T17:06:22 #kisslinux <dilynm> By the gods. My patch worked
2020-05-12T17:06:49 #kisslinux <dilynm> I hate computers so much
2020-05-12T17:19:05 #kisslinux <ominous_anonymou> sounds like its a good time for a beer break XD
2020-05-12T17:22:30 #kisslinux <dilynm> I need it
2020-05-12T17:38:04 #kisslinux <perish> https://www.youtube.com/watch?v=HOtgF3eCn-Y systemd
2020-05-12T18:37:47 #kisslinux <E5ten> konimex: for gtk3, why don't you use meson to avoid the GNU make dep?
2020-05-12T18:53:23 #kisslinux <dylan02> o/
2020-05-12T18:53:56 #kisslinux <dylan02> perish: You can patch it out.
2020-05-12T18:54:23 #kisslinux <dilynm> o/
2020-05-12T19:04:47 #kisslinux <perish> Oh, ok
2020-05-12T19:07:07 #kisslinux <dylan02> Which packages exactly have the dependency?
2020-05-12T19:07:17 #kisslinux <dylan02> I'd like to help you get rid of those dependencies.
2020-05-12T19:07:41 #kisslinux <perish> lemme check
2020-05-12T19:07:57 #kisslinux <dylan02> I know there's libxfce4util, but are there any others?
2020-05-12T19:08:25 #kisslinux <perish> I feel like it's just a dropdown dependency
2020-05-12T19:08:38 #kisslinux <dylan02> I think that's it.
2020-05-12T19:08:40 #kisslinux <perish> Lets see
2020-05-12T19:08:54 #kisslinux <perish> I've removed intltool and will try to build the packages
2020-05-12T19:09:11 #kisslinux <dylan02> configure fails
2020-05-12T19:09:36 #kisslinux <perish> Aye, xfconf doesn't build due to the config failing
2020-05-12T19:09:47 #kisslinux <perish> Do you think it'd work to use the texinfo method?
2020-05-12T19:12:54 #kisslinux <perish> Let's see
2020-05-12T19:13:24 #kisslinux <perish> Texinfo method works for xfconf
2020-05-12T19:13:51 #kisslinux <perish> Also, xfconf doesn't seem to even try linking dbus, so that seems good
2020-05-12T19:13:59 #kisslinux <perish> We'll see if it functions without soon
2020-05-12T19:15:43 #kisslinux <perish> Since most builds are generic, we can just symlink them
2020-05-12T19:17:25 #kisslinux <perish> xfce4ui fails due to a .desktop file that wasn't found, we could generate this and include
2020-05-12T19:17:43 #kisslinux <dylan02> oof
2020-05-12T19:17:47 #kisslinux <dylan02> This won't work at all
2020-05-12T19:17:56 #kisslinux <perish> Oh?
2020-05-12T19:18:22 #kisslinux <dylan02> It's a big part of the build system
2020-05-12T19:18:27 #kisslinux <perish> Ouch
2020-05-12T19:18:36 #kisslinux <perish> Well, I'll symlink the builds anyway
2020-05-12T19:18:39 #kisslinux <perish> Long overdue
2020-05-12T19:28:00 #kisslinux <perish> HM
2020-05-12T19:28:07 #kisslinux <perish> I may have messed up the symlinks
2020-05-12T19:28:16 #kisslinux <perish> Ouch
2020-05-12T19:28:27 #kisslinux <perish> How do I properly get git to symlink
2020-05-12T19:30:36 #kisslinux <mattx433> Doesn't Git automatically do that?
2020-05-12T19:31:12 #kisslinux <perish> Seems to not have
2020-05-12T19:31:37 #kisslinux <dilynm> It just stores it as a file with the name of what the link points to :X
2020-05-12T19:31:41 #kisslinux <perish> Aye
2020-05-12T19:31:43 #kisslinux <dilynm> You could hard link it haha
2020-05-12T19:31:46 #kisslinux <perish> It has things around that
2020-05-12T19:31:56 #kisslinux <perish> But I don't recall how to enable those
2020-05-12T19:32:23 #kisslinux <perish> https://github.com/periish/kiss-xfce4/blob/master/kiss-xfce4/libxfce4ui/build see this as to what has happened
2020-05-12T19:33:05 #kisslinux <dilynm> Change core.symlinks to true?
2020-05-12T19:34:40 #kisslinux <perish> Oh?
2020-05-12T19:34:48 #kisslinux <perish> Where's the git config location again
2020-05-12T19:35:04 #kisslinux <himmalerin> .git/config I think
2020-05-12T19:35:35 #kisslinux <dilynm> You can change it for just the repo; `git config core.symlinks true`
2020-05-12T19:35:42 #kisslinux <dilynm> Or do it globally because why not
2020-05-12T19:37:34 #kisslinux <perish> No change, it seems
2020-05-12T19:37:49 #kisslinux <perish> Symlinks are still
2020-05-12T19:37:50 #kisslinux <perish> Like that
2020-05-12T19:38:48 #kisslinux <mcf> perish: the symlink target is just a string. if you want it to work in a repository, use a relative path
2020-05-12T19:39:28 #kisslinux <perish> Ah
2020-05-12T19:39:52 #kisslinux <perish> The relative paths produced broken symlinks in my actual local repo
2020-05-12T19:40:40 #kisslinux <mcf> that doesn't make sense to me. what symlink target did you use?
2020-05-12T19:41:04 #kisslinux <perish> `xfconf/build libxfce4ui/build`, for example
2020-05-12T19:41:21 #kisslinux <perish> also tried `./xfconf/build libxfce4ui/build`
2020-05-12T19:42:04 #kisslinux <mcf> the path should be relative to the symlink, so `ln -s ../xfconf/build libxfce4ui/build`
2020-05-12T19:42:53 #kisslinux <perish> Ah
2020-05-12T19:43:51 #kisslinux <perish> Bless
2020-05-12T19:45:50 #kisslinux <onodera> dylan02: kiss idea, maybe prettyfying the kiss u output?
2020-05-12T19:46:05 #kisslinux <onodera> just showling file modifications and such rather than all the other git git output
2020-05-12T19:48:15 #kisslinux <perish> That would be a nice idea, onodera
2020-05-12T19:54:41 #kisslinux <perish> Let's give lightdm a try
2020-05-12T19:58:52 #kisslinux <perish> Oh boy
2020-05-12T19:58:54 #kisslinux <perish> PAM
2020-05-12T20:03:26 #kisslinux <merakor> dylan02: as of today kiss has over a thousand commits
2020-05-12T20:04:42 #kisslinux <dilynm> Is there a login manager that doesn't use PAM?
2020-05-12T20:05:16 #kisslinux <merakor> Without being exactly sure, I don't think so
2020-05-12T20:05:26 #kisslinux <perish> Greetd might but all the greeters use wayland, plus it uses rust
2020-05-12T20:05:34 #kisslinux <merakor> I have tried lots of login managers without seeing one
2020-05-12T20:07:20 #kisslinux <perish> Perhaps xenodm
2020-05-12T20:07:27 #kisslinux <perish> But that probably doesnt have a linux port
2020-05-12T20:07:29 #kisslinux <dilynm> Thank God for Ccache. Stdint.h is missing from, so far, 3 files. One of which is just over halfway through the build. It took three hours to get there
2020-05-12T20:07:51 #kisslinux <dilynm> Perish: there's your next project :P
2020-05-12T20:08:57 #kisslinux <perish> Oh god
2020-05-12T20:09:01 #kisslinux <perish> My next project was a font
2020-05-12T20:09:06 #kisslinux <perish> Then finishing my bars
2020-05-12T20:09:11 #kisslinux <perish> Then maybe a window manager
2020-05-12T20:09:16 #kisslinux <perish> Not an openbsd port
2020-05-12T20:12:11 #kisslinux <merakor> I know exactly how you are feeling
2020-05-12T20:53:26 #kisslinux <micro_O> so i dont have gpg installed, whichso i dont have gpg installed, and kiss u fails because i think git is requiring gpg
2020-05-12T20:53:54 #kisslinux <micro_O> does that mean, transitively, that kiss requires gpg? or that i can unconfigure that
2020-05-12T20:54:56 #kisslinux <konimex> E5ten: for some reason building with meson gave this: https://termbin.com/tyd8
2020-05-12T20:58:07 #kisslinux <micro_O> ahh i can git config merge.verifySignatures false
2020-05-12T20:58:10 #kisslinux <micro_O> neat
2020-05-12T22:11:08 #kisslinux <E5ten> dylan02: ever considered allowing kiss to be used a shell library for other kiss related scripts, like at the end you could do something like 'case ${0##*/} in kiss) main "$@"; esac' so it could be sourced from a script not called kiss? or you could do a KISS_LIBRARY variable which would be set by the calling script, and you could do '[ "${KISS_LIBRARY}" ] || main "$@"'
2020-05-12T22:13:49 #kisslinux <E5ten> like this http://ix.io/2lQ7
2020-05-12T22:15:46 #kisslinux <merakor> I tested something like that myself
2020-05-12T22:17:31 #kisslinux <merakor> I don't find it much beneficial myself
2020-05-12T22:18:02 #kisslinux <merakor> You also need to change some functions like `die()`
2020-05-12T22:19:03 #kisslinux <E5ten> die doesn't seem all that kiss specific to me?
2020-05-12T22:19:03 #kisslinux <merakor> But it would be beneficial for purposes I am not seeing right now
2020-05-12T22:19:50 #kisslinux <merakor> The issue with die is if you want to run a kiss function, but you are okay with it failing
2020-05-12T22:19:54 #kisslinux <merakor> die will kill the script
2020-05-12T22:20:12 #kisslinux <merakor> for example if you source kiss as a library and call pkg_find
2020-05-12T22:20:24 #kisslinux <merakor> And the package doesn't exist, the script will exit
2020-05-12T22:21:32 #kisslinux <E5ten> I mean sure, that restricts the script from using pkg_find if it wants to be ok with failure, but I'm sure some purposes would still be able to use that and be ok with requiring the package to exist
2020-05-12T22:22:13 #kisslinux <merakor> Yeah you could also do a [ $KISS_LIBRARY ] || exit 1 inside the die function
2020-05-12T22:22:19 #kisslinux <E5ten> like allowing that usage first would need to be the first step, and then when issues like that arose, e.g. someone wanting to use pkg_find without failing on a missing package, that could be changed in a relevant way
2020-05-12T22:22:22 #kisslinux <E5ten> good point
2020-05-12T22:22:57 #kisslinux <E5ten> you could also have KISS_LIBRARY be able to be set to like 2 to disable those kinds of exits, so someone could either use it with the included error handling, or optionally disable it and manage that themselves
2020-05-12T22:23:16 #kisslinux <merakor> Yeah, I agree it can make it easier to integrate contrib scripts with kiss functions as well
2020-05-12T22:23:36 #kisslinux <E5ten> so KISS_LIBRARY being non-zero just doesn't run main, setting it above 1 would disable functions exiting in certain cases
2020-05-12T22:23:53 #kisslinux <merakor> That's a good idea
2020-05-12T22:26:14 #kisslinux <E5ten> maybe there could be 2 tiers of die, cuz there are probably certain exits that should be enforced even if it's being used as a library
2020-05-12T22:26:30 #kisslinux <E5ten> the lower level doesn't exit if KISS_LIBRARY is above 1, and the second always exits
2020-05-12T22:27:10 #kisslinux <merakor> There can be a value specified as the first argument of die. Later arguments are just the die messages.
2020-05-12T22:27:24 #kisslinux <E5ten> makes sense
2020-05-12T22:27:53 #kisslinux <E5ten> I assume it should still print the error message and just not exit?
2020-05-12T22:28:00 #kisslinux <E5ten> like return 1 instead of exit 1?
2020-05-12T22:28:15 #kisslinux <merakor> return 1 wouldn't work
2020-05-12T22:28:27 #kisslinux <merakor> as return only acts for the current function
2020-05-12T22:28:36 #kisslinux <merakor> Oh it would work
2020-05-12T22:28:37 #kisslinux <merakor> sorry
2020-05-12T22:29:04 #kisslinux <E5ten> I just mean so the calling function can check its error I guess? I guess if die is running there must be an error, but it would allow further chaining of ||
2020-05-12T22:29:15 #kisslinux <merakor> Wait, it wouldn't work :D
2020-05-12T22:29:27 #kisslinux <merakor> so die includes return 1
2020-05-12T22:29:36 #kisslinux <merakor> return 1 only acts for die
2020-05-12T22:29:48 #kisslinux <merakor> so the function you are using die with isn't affected
2020-05-12T22:30:37 #kisslinux <merakor> But checking for function output would work
2020-05-12T22:30:40 #kisslinux <merakor> But wouldn't that kill the whole purpose of die?
2020-05-12T22:30:41 #kisslinux <E5ten> I mean so a calling function in kiss could do like this to do something on error when the script isn't exiting, like returning, so instead of '[ condition ] || die "$1" "text"' you might do '[ condition ] || die "$1" "text" || return'
2020-05-12T22:31:32 #kisslinux <E5ten> cuz even if the script shouldn't exit the function might need to return to prevent its further actions that work incorrectly when something within fails
2020-05-12T22:32:06 #kisslinux <merakor> Yeah that would work
2020-05-12T22:32:09 #kisslinux <merakor> Since die would return 1
2020-05-12T22:32:26 #kisslinux <E5ten> yeah, that's what I'm suggesting
2020-05-12T22:32:47 #kisslinux <E5ten> http://ix.io/2lQe like this would work I mean
2020-05-12T22:33:13 #kisslinux <E5ten> oh wait you'd have to assign switch the arguments to log
2020-05-12T22:33:39 #kisslinux <E5ten> and also change every die to have their first arg be 0 or 1, 0 if it shouldn't exit in library mode and 1 if it should
2020-05-12T22:34:48 #kisslinux <merakor> https://termbin.com/7x58
2020-05-12T22:34:56 #kisslinux <merakor> I thought something like this
2020-05-12T22:35:05 #kisslinux <E5ten> fair enough
2020-05-12T22:35:26 #kisslinux <merakor> Since die is supposed to fail, we can basically return 1 if we haven't exited
2020-05-12T22:35:27 #kisslinux <E5ten> http://ix.io/2lQg
2020-05-12T22:36:07 #kisslinux <E5ten> now if this is gonna be a thing, there need to be decisions for each die call on what should exit and what should not
2020-05-12T22:36:22 #kisslinux <E5ten> and if it shouldn't, on if the function should still return or not
2020-05-12T22:36:53 #kisslinux <E5ten> although initially each call could be given a 1 argument, to keep behaviour as is, and then over time it could be seen what would be useful not to have exit
2020-05-12T22:37:10 #kisslinux <merakor> Yeah I agree
2020-05-12T22:37:56 #kisslinux <merakor> I would say that pkg_find shouldn't exit if it doesn't find a given package
2020-05-12T22:38:26 #kisslinux <merakor> Or maybe it should since you can't continue package operations
2020-05-12T22:38:30 #kisslinux <merakor> :D
2020-05-12T22:39:24 #kisslinux <E5ten> well it doesn't have a return 1 case, so if it returned non-0, but didn't exit, the caller would know it failed and act accordingly
2020-05-12T22:40:00 #kisslinux <E5ten> if a function has multiple failure modes that don't exit when KISS_LIBRARY>1, there could be different documented return codes even
2020-05-12T22:45:39 #kisslinux <E5ten> I'll send my newest version soon, but basically I changed it to KISS_LIBRARY specifically being 2 to disable die in certain scenarios instead of "above 1", to leave it open for future value of KISS_LIBRARY doing certain other things
2020-05-12T22:50:24 #kisslinux <merakor> I thought calling return without a number would return 0, no?
2020-05-12T22:51:27 #kisslinux <E5ten> are you talking about something in the patch, or the part I typed in chat with the '|| return' after a function call?
2020-05-12T22:52:03 #kisslinux <E5ten> if the latter, return with no value returns what the previous action returned, and since it's after an ||, the previous action had to return non-zero, so the functions return value is passed along
2020-05-12T22:52:40 #kisslinux <merakor> Yeah, I was talking about the latter
2020-05-12T22:53:19 #kisslinux <merakor> Okay I forgot that return without a number returned the previous action
2020-05-12T22:53:58 #kisslinux <E5ten> just made a PR, I don't have a kiss system so if you could test it I'd appreciate it lol
2020-05-12T22:54:19 #kisslinux <merakor> Sure I'll test it out now
2020-05-12T23:01:13 #kisslinux <merakor> I didn't quite get the math function
2020-05-12T23:01:35 #kisslinux <merakor> Doesn't it always return 1 in our case?
2020-05-12T23:10:31 #kisslinux <E5ten> when KISS_LIBRARY is 2, and $1 is 0, that math thing will evaluate to 0, because both sides of the || are false, so the [ will be true, and exit won't run, and it'll return, when KISS_LIBRARY is not 2, or the first argument is non-zero, at least one side of || will be true, the $(( won't be 0, the [ will fail, and the script will exit
2020-05-12T23:11:07 #kisslinux <E5ten> basically when either of the contents of $(()) are true, the exit happens
2020-05-12T23:14:21 #kisslinux <merakor> Oh I get it
2020-05-12T23:15:03 #kisslinux <merakor> I was thinking they were like reverse logical operators since 0 return code is true in shell
2020-05-12T23:15:17 #kisslinux <merakor> I was thinking like 0=true 1=false
2020-05-12T23:15:22 #kisslinux <merakor> That's why I was confused there
2020-05-12T23:15:38 #kisslinux <E5ten> ah, gotcha, nah since the arithmetic is the same as C 0=false and anything else is true
2020-05-12T23:16:06 #kisslinux <E5ten> once you're done testing leave a review with any issues you have if you can
2020-05-12T23:16:35 #kisslinux <merakor> Sure, I am testing some function behaviour now
2020-05-12T23:23:00 #kisslinux <merakor> `cdpkg() { cd $(pkg_find "$1") ;}` for absolute laziness
2020-05-12T23:40:54 #kisslinux <E5ten> http://ix.io/2lQt mind giving this a try on top of the PR as a proof of concept for this being used?
2020-05-12T23:46:41 #kisslinux <E5ten> separately, in regards to pkg_find, I see that it's almost always it's called in a subshell, I wonder if it might be better to, instead of it printing the found value to stdout, it could store it in a pkg_find_dir variable or something, and that variable is only defined as safe to reference between the call to pkg_find and any other function call, that way instead of numerous subshell invocations, that variable's value could
2020-05-12T23:46:41 #kisslinux <E5ten> just be stored in some other variable by the caller right after use, or if only used once right after the call, it could be used immediately after
2020-05-12T23:47:08 #kisslinux <E5ten> that would also allow the exits and return values and stuff to propogate correctly instead of being ignored cuz pkg_find is run in $()
2020-05-12T23:48:48 #kisslinux <merakor> Yeah, that works as well
2020-05-12T23:49:39 #kisslinux <merakor> pkg_find test || echo no
2020-05-12T23:49:48 #kisslinux <merakor> ERROR Package 'test' not in any repository
2020-05-12T23:49:48 #kisslinux <merakor> no
2020-05-12T23:50:50 #kisslinux <E5ten> should die (with KISS_LIBRARY=2 and the first arg being 0) also not print the error message as well as not exiting?
2020-05-12T23:51:19 #kisslinux <E5ten> cuz I feel like making the caller deal with the error message doesn't make sense because the caller doesn't know why it returned necessarily
2020-05-12T23:52:28 #kisslinux <E5ten> like I feel like in that case it'd just make sense for the caller to not be having something with output on the other side of the || unless it's an error message that makes sense along with the other right?
2020-05-12T23:53:03 #kisslinux <merakor> Yeah, but for stuff like that you could redirect stderr to null
2020-05-12T23:53:11 #kisslinux <E5ten> true
2020-05-12T23:53:34 #kisslinux <E5ten> so you agree with leaving error messages untouched regardless of KISS_LIBRARY
2020-05-12T23:53:43 #kisslinux <E5ten> meant to end that with a ?
2020-05-12T23:54:16 #kisslinux <merakor> If you are using a script that gets a package name as an argument pkg_find error looks good
2020-05-12T23:54:35 #kisslinux <merakor> I agree that it should be untouched
2020-05-12T23:54:35 #kisslinux <E5ten> yeah
2020-05-12T23:57:00 #kisslinux <merakor> I need to go now, I'll check up on the PR tomorrow
2020-05-12T23:57:20 #kisslinux <merakor> o/
2020-05-12T23:57:21 #kisslinux <E5ten> sounds good, probably won't be changed cuz I don't think any of this further stuff we discussed belongs in the same PR
2020-05-12T23:57:40 #kisslinux <merakor> Yeah, I think those need more discussion