ChanServ changed the topic of #kisslinux to: Unnofficial KISS Linux community channel | https://kisscommunity.bvnf.space | post logs or else | song of the day https://vid.puffyan.us/H7PvgY65OxA
soliwilos has quit [Remote host closed the connection]
soliwilos has joined #kisslinux
soliwilos has quit [Ping timeout: 255 seconds]
soliwilos has joined #kisslinux
Torr has quit [Quit: leaving]
<wael_> Hi
<niceguy5000[m]> HI
<niceguy5000[m]> Is Unix dead?
<wael_> Probably, but BSD isnt
<testuser[m]> Hi
Torr has joined #kisslinux
sad_plan has joined #kisslinux
<testuser[m]> illiliti: is there an accurate way to determine if disk has enough space for pkg installation?
<testuser[m]> for adding a check
<testuser[m]> also i need to look into pipewire hotplug, forgot about it
sam_sepi0l has joined #kisslinux
<illiliti> perhaps you can parse output of df "${KISS_ROOT:-/}"
<illiliti> not sure if it's accurate way though
<illiliti> imagine user has separate /usr
<illiliti> to get accurate size, you have to iterate over df output and take into the account these separate mountpoints
<illiliti> i believe this is the only way
<illiliti> oh
<illiliti> also pseudo filesystems
<illiliti> you need to ignore them somehow
<testuser[m]> hmm
<testuser[m]> how do current pkg managers do it
<Ellowee[m]> Your'd have to store size of build tree in a file and compare against free on root
<Ellowee[m]> * Your'd have to store size of build tree in a file and compare against free on root
<Ellowee[m]> (A post build hook?)
<illiliti> not that simple because mountpoints
<illiliti> idea: iterate over package's manifest, get size of each top-level directory and run df -P on that directory in KISS_ROOT to get available size, compare
<illiliti> but as you see it is not perfect because we don't handle nested mountpoints
<illiliti> i wish df have a flag to print nested mountpoints
<illiliti> that would simplify things
<illiliti> you can still handle nested mountpoints though
<illiliti> parse parse parse df -P output
<phoebos> hei illiliti does the opengroup have plans to require make to set a PWD macro in 202x?
<illiliti> no clue
<illiliti> why do you ask
<phoebos> would be useful and BSD and GNU have incompatible syntaxes for it
<illiliti> i see
<illiliti> smake also has CURDIR
<illiliti> i'll send a proposal when i get free time
<phoebos> nice
<phoebos> let me know if i can help
noocsharp has joined #kisslinux
rohan has joined #kisslinux
<sad_plan> is there a floating wayland wm thats reasonably good? I only know of spkp, which it seems its really working :p
<testuser[m]> I don't understand your question. Monero doesn't need any wrappers to use LMDB. Nor does LMDB have any memory management bugs, so a language like rust would only bloat it and slow it down.
<phoebos> sad_plan: wayfire?
<sad_plan> phoebos: hm, isnt that what dilyn used earlier? Ill check it out
<sad_plan> *3D*. fancy stuff
<sad_plan> hikari was the one which I thought about, but dilyn did use wayfire
<illiliti> phoebos: wait, what make should put into CURDIR if run with -f path/to/Makefile
<illiliti> implementations seem to not handle this case
sad_plan has quit [Quit: nyaa~]
<phoebos> illiliti: make -C is an explicit chdir, -f is just using a different makefile, so I think CURDIR should not be changed by -f but should be by -C
<phoebos> bmake does this
<phoebos> gnu make distinguishes PWD and CURDIR when doing -C
<phoebos> in that case, PWD is where you run it and CURDIR is where make is running (-C CURDIR)
<phoebos> weird
<phoebos> oh no i forgot gmake doesn't set PWD
<illiliti> -C is no problem
<illiliti> i afraid -f will break CURDIR
<illiliti> cd /tmp && make -f /tmp/project/Makefile
<phoebos> why? because a makefile using CURDIR will expect CURDIR to be the same dir as it's written in?
<illiliti> yes2
<phoebos> then there should be a note that in that case it is necessary to do cd dir; make rather than make -f dir/Makefile
<phoebos> > in particular note that if you include files from other directories the value of CURDIR does not change
<phoebos> is PWD a better name because of the incompatibility with CURDIR/.CURDIR
<illiliti> PWD would be an invention; not suitable for addition
rohan has quit [Ping timeout: 264 seconds]
<illiliti> which incompatibility btw? i only see that bmake need leading dot, but that's minor
rohan has joined #kisslinux
rohan has quit [Ping timeout: 264 seconds]
<illiliti> oh wait, PWD is documented in bmake. then it would not be invention
<phoebos> yeah i just meant the leading dot