acheam changed the topic of #kisslinux to: Unnofficial KISS Linux community channel | https://kisscommunity.org | post logs or else | song of the day https://vid.puffyan.us/epbF8WCB4y4
<acheam> cem: why do you do this temp file thing instead of just ". $(command -v kiss)" https://github.com/kiss-community/mkrootfs/blob/kiss-new/mkrootfs.sh#L7
<acheam> also why use sed instead of cp?
<illiliti> > library
<illiliti> temp file can be replaced with eval i guess
<illiliti> eval "$(sed "${kissln}d" "$kissloc")"
<acheam> I still don't understand.... is the original not just copying kiss into a temp file and sourcing it?
<acheam> why not just source the original kiss file?
<illiliti> because kiss calls main function and sed removes it so that it can be used as library
<acheam> ah thanks
<acheam> oh thats literally written in the comment
<acheam> dont know how I missed that
<illiliti> it is a dirty hack of course, but there's no other way
<illiliti> the proper way would be having KISS_LIBRARY variable in kiss that disable execution of main function
<illiliti> but afaik Dylan was against it, don't remember why...
<phoebos> eval "$(sed '/^main "\$@"/d' "$(command -v kiss)")"
<phoebos> or even sed '$d' /usr/bin/kiss
<acheam> I wouldn't assume /usr/bin/kiss
<acheam> for a while I put kiss in sbin, and have often had a kiss that I was messing around with higher in my path
<cem> uhmm because I was an idiot when I wrote that particular line
<cem> what I wanted to go for was definitely "sed '$d'"
<cem> my mkrootfs script is old and pretty bad honestly, but it was working so I always delayed revising it
ejjdhfjsu has quit [Remote host closed the connection]
mahmutov has quit [Ping timeout: 248 seconds]
illiliti has quit [Read error: Connection reset by peer]
illiliti_ has joined #kisslinux
illiliti_ is now known as illiliti
<testuser[m]> Hi
<acheam> hi
illiliti has quit [Quit: later]
jslick has quit [Quit: Ping timeout (120 seconds)]
jslick has joined #kisslinux
Guest32 has joined #kisslinux
Guest32 has quit [Client Quit]
ella-0 has joined #kisslinux
ella-0_ has quit [Ping timeout: 268 seconds]
zlg has quit [Ping timeout: 252 seconds]
phoebos[m] has quit [Quit: You have been kicked for being idle]
ejjdhfjsu has joined #kisslinux
ejjdhfjsu has quit [Remote host closed the connection]
mahmutov has joined #kisslinux
zlg has joined #kisslinux
illiliti has joined #kisslinux
<noocsharp> 1.2.3
phoebos[m] has joined #kisslinux
ejjdhfjsu has joined #kisslinux
progenyx has quit [Quit: progenyx]
doggy_breath has joined #kisslinux
<doggy_breath> OK, I'm buying a (used) laptop and going to try to install KISS on it. It will probably end up being some ancient i5 thing with 4GB ram and 256GB storage
<doggy_breath> Will I be able to stay connected to this channel during the install process in case I get stuck?