<dilyn>
he's like a weird cross between a fud spreader, a freelance microblogger, and a bad researcher
<dilyn>
but that's like, 80% of the these communities we find ourselves in sometimes :V
<dilyn>
if people injected fewer opinions into their questions they might garner more sympathy, but at this point so much has been spelled out in easy to access places... it truly boggles the mind (:
<necromansy>
what..what is that post
<GalaxyNova>
I have no idea
<GalaxyNova>
it hurts my brain
<msk[m]>
"the rat" lol
<msk[m]>
Never heard someone call it that
stjohn has quit [Ping timeout: 245 seconds]
mTvare6 has joined #kisslinux
mTvare6 has quit [Client Quit]
stjohn has joined #kisslinux
necromansy has quit [Quit: nyaa~]
akspecs has joined #kisslinux
<akspecs>
hello everybody!
<testuser[m]>
hi
<akspecs>
i've been looking at kiss linux for some time now and am curious to try it
<akspecs>
i did want to ask some folks a couple of things, though
<testuser[m]>
ask
stjohn has quit [Ping timeout: 268 seconds]
<akspecs>
i get to some extent why powerusers shy away something like systemd
<akspecs>
i don't understand why users similarly minded distros to kiss shy away from gnu
<akspecs>
s/users/users from/
<cotangent>
<akspecs> i don't understand why users from similarly minded distros to kiss shy away from gnu
stjohn has joined #kisslinux
<testuser[m]>
You mean to ask why kiss doesn't use gnu utils ?
<akspecs>
i imagine someone can write their own build script for them, but the motivating philsophy behind it intrigues me
<akspecs>
personally, i have a lot of muscle memory with gnu coreutils
<testuser[m]>
They're already packaged
<testuser[m]>
In community
<testuser[m]>
They're not used since gnu has too much feature creep in their utils beyond what's specified by posix
GalaxyNova has quit [Ping timeout: 248 seconds]
<testuser[m]>
And on kiss everything is meant to be portable (only what's POSIX) , so there's no need for utils that implement extra features
<akspecs>
not to sound too ignorant on the matter, but why strive towards an ideal like posix?
<testuser[m]>
Portability, avoids lock-in to specific set of utilities
<testuser[m]>
you can run kiss the package manager on any bsd or whatever if you really want to, without much modification
<akspecs>
i get that in theory, a posix compliant shell script can be portable, but what about the fact that some modern systems aren't shipping with posix compatability, or that it's an old standard
<testuser[m]>
Example ? I don't think that's the case
<akspecs>
more specifically i can point to that a lot of modern software is written without any regard to posix
<akspecs>
some of which is adequate software
<akspecs>
let me phrase it differently
<akspecs>
let's say that there's a more convinient and familiar way of doing things (that is fairly widespread) -- why insist on the posix way of doing things?
<akspecs>
e.g. gnu awk and gnu sed
<Erus_Iluvatar>
akspecs: what if tomorrow the linux kernel stops being maintained
<Erus_Iluvatar>
and the tools you rely on have a dependancy on it
<akspecs>
is anything guranteed to be maintained forever, though?
<Erus_Iluvatar>
don't lock yourself in a corner voluntarily though
<testuser[m]>
That's the point, to avoid depending on a a specific set of tools as much as possible. If other software is not portable, you should strive to keep yours portable still
<akspecs>
do you guys make a living working with *nix systems?
<akspecs>
in my example, i won't be the one to convince my co-workers to stop writing their so-called shell scripts full of bashisms
<akspecs>
especially if a majority of them do so
<Erus_Iluvatar>
akspecs: work is a different beast
<Erus_Iluvatar>
if you expect bash to always be present on the systems you will be working on, go ahead and use all the niceties it'll give you
<testuser[m]>
If you're making something only for a specific environment, and non-portable tools are guaranteed to be present there, then use it
<testuser[m]>
eg those scripts won't work out of the box if you try to run them in an alpine container
<Erus_Iluvatar>
thanks, better wording than i could muster
<akspecs>
how familiar are some of you with perl?
<testuser[m]>
I think almost everyone hates perl here
<akspecs>
fairly agreeable, but there still may be a useful number of perl scripts out there, no?
<testuser[m]>
Yeah, and you just install perl if you want to use them
<akspecs>
maybe i'm misunderstanding the philosphy
<akspecs>
s/philosphy/philosophy/
<cotangent>
<akspecs> maybe i'm misunderstanding the philosophy
<testuser[m]>
I don't get what you want to say, do you want the more convinient utils to be present in base ?
<akspecs>
let me get up to speed here -- is cotangent a bot?
<testuser[m]>
Yeah
<akspecs>
sweet!
<testuser[m]>
Btw i think you overestimate the amount of non-portability in software. Everything in KISS's official repo is just to get an environment up to a web browser (firefox), and the bare minimum packages to achieve that are included
<testuser[m]>
Out of those, only 2 need perl (ff and openssl) and none have a lock-in into gnu utilities, so they're not included in base
<testuser[m]>
community is different
mTvare6 has joined #kisslinux
mTvare6 has quit [Quit: WeeChat 3.2]
<mTvare[m]>
I am still here 😎
mobinmob has joined #kisslinux
gtms has joined #kisslinux
Jason123santaOnI has quit [Ping timeout: 245 seconds]
gtms_ has joined #kisslinux
gtms has quit [Ping timeout: 240 seconds]
w1ke has joined #kisslinux
w1ke has quit [Quit: Lost terminal]
mobinmob has quit [Quit: Connection closed for inactivity]
gtms_ has quit [Remote host closed the connection]
Uks2 has quit [Ping timeout: 245 seconds]
Uks2 has joined #kisslinux
Uks2 has quit [Ping timeout: 252 seconds]
Uks2 has joined #kisslinux
Uks2 has quit [Read error: Connection reset by peer]
Uks2 has joined #kisslinux
soliwilos has quit [Quit: nyaa~]
soliwilos has joined #kisslinux
stjohn has left #kisslinux [#kisslinux]
barpthewire has quit [Ping timeout: 268 seconds]
barpthewire has joined #kisslinux
eyepatchOwl has joined #kisslinux
<eyepatchOwl>
Huh. This was a good week to check back in on kiss. Glad to see revitalization.
<acheam>
When was there death?
mobinmob has joined #kisslinux
mahmutov has joined #kisslinux
stjohn has joined #kisslinux
eyepatchOwl has quit [Quit: Connection closed for inactivity]
mobinmob has quit [Quit: Connection closed for inactivity]
j0hnny has quit [Ping timeout: 245 seconds]
mobinmob has joined #kisslinux
Uks3 has joined #kisslinux
Uks2 has quit [Ping timeout: 268 seconds]
Guest5 has joined #kisslinux
<Guest5>
Is it possible to run a cmd before a script/process in killed?
<Guest5>
Like within the script detect that it would be killed. Like trap I guess
<Guest5>
I know u could do trap with Ctrl+C but not sure if you called the "kill" command