#kisslinux

Unnofficial KISS Linux community channel | https://kisscommunity.bvnf.space | post logs or else | song of the day https://vid.puffyan.us/H7PvgY65OxA
Earlier messages
ioraffjoined
<illiliti>i mean in general. if i haven't missed anything, chroot(KISS_ROOT) is a cleaner way
<illiliti>but as you noted, how kiss would access ~/.cache/kiss/bin. does it need such access
ioraffquit (Client Quit)
<illiliti>re adding users, imo packages shouldn't modify anything in /etc
<illiliti>they can only add new files and/or modify only their own files
<illiliti>that's something we should enforce in sandbox
<testuser[m]>illiliti: what about openssl certificate updaye
<testuser[m]>illiliti: what about openssl certificate updaye
<illiliti>it's ok cuz /etc/ssl/* is owned by openssl
<illiliti>to be exact, openssl is a sole app that writes to /etc/ssl/*
<illiliti>things get messy when apps start write to /etc/shells
<illiliti>or /etc/passwd
<illiliti>and on remove, they don't cleanup their shit
<sad_plan>midfavila: I managed to build tinyx statically, if youre interested in doing so yourself
<midfavila>that would be something I'd be interested in seeing, yeah
<sad_plan>set XSERVERCFLAGS_CFLAGS to --static. maybe -static works for you, but for me it didnt seem to work.
<sad_plan>you may also have to add some libs to XSERVERLIBS_LIBS aswell. I had to add libz, freetype and harfbuzz and libpng. I also set *.a aswell to begin with. dunno if it made any difference tbh.
<midfavila>could you package the changes and send me a copy?
<sad_plan>just the buildscript?
<midfavila>correct
<sad_plan>http://0x0.st/oJqB.sh there you go
<midfavila>thanks, I'll fiddle with it next time I'm looking at tinyx
<midfavila>for now I've put any X-related stuff off to the side
<sad_plan>youre welcome :D
<sad_plan>alot of other stuff to figure out first?
<midfavila>no, stuff that I'm not capable of figuring out right now
<midfavila>tinycc doesn't generate executables that use motif or athena properly
<midfavila>that's not something I can fix
<midfavila>xwx
<sad_plan>well I cant help you there unfortunatly.
<sad_plan>do you have to use those though?
<sad_plan>I mean, if I cant use tool x, then sometimes I look for tool y or z instead, that might fit the bill
<midfavila>do i have to use athena/motif, or do i have to use tcc?
<sad_plan>athena/motif
<midfavila>technically no to the former, yes for the latter
<midfavila>i could just use programs that exclusively use xlib directly
<midfavila>but that's a horrible idea
<midfavila>motif and athena are the only toolkits that my system can build
<midfavila>so
<sad_plan>but they dont generate executables, so dont build properly now do they? but whats wrong with using xlibs tools?
<sad_plan>I mostly like tools that depend purly on xlibs, as theyre likely simpler to build statically..
<midfavila>the code is valid and some athena programs work as they should
<sad_plan>some are anyway, not everyone
<midfavila>this is a problem in tcc that needs to be resolved
<sad_plan>hm, ok
<midfavila>anyway, while i can appreciate that mindset, going toolkit-less isn't viable for larger-scale projects, I think
<sad_plan>im not saying you should drop something you initially need, but if some other tool can accomplish what you want, why not give that a try? I get that some tools might not be easily replacable though.
<sad_plan>also dont waste too much time on 1 issue. if you cant figure it out, do something else for some time, then come back to it afterwards
<sad_plan>I do that all the time. makes troublesome issues.. abit less troublesome imo
Later messages