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
rohan has quit [Ping timeout: 260 seconds]
rohan has joined #kisslinux
GalaxyNova_ has joined #kisslinux
GalaxyNova_ has quit [Client Quit]
ella-0_ has joined #kisslinux
rohan has quit [Ping timeout: 268 seconds]
rohan has joined #kisslinux
ella-0 has quit [Ping timeout: 268 seconds]
rohan has quit [Ping timeout: 268 seconds]
<testuser[m]> Hi
<GalaxyNova> hi
chomwitt has joined #kisslinux
sereg has quit [Ping timeout: 252 seconds]
<wael_> Hi
<GalaxyNova> anyway to continue on my rant from earlier, standards are definetly needed to have a useable computing ecosystem
<GalaxyNova> but top-down designed standards are bad
<GalaxyNova> imo standards should be decided uppon by the implementors
<GalaxyNova> midfavila
<GalaxyNova> i think they're offline
GalaxyNova has quit [Remote host closed the connection]
<macslash1[m]> Meow
<macslash1[m]> I feel like in the case of linux legacy is becoming somewhat more relevant as like almost all servers in the world use it so at some point old systems are just going to become unmaintained thats just a fact and thus some sense of the system must be kept to allow it to run
<testuser[m]> How can u have an impl before a standard is made
<macslash1[m]> Maybe its not very true now but you can see it with incredibly old windows servers that have like a 10 dollar budget lol
<testuser[m]> has anyone thought of managing dotfiles with kiss
<testuser[m]> like setting KISS_ROOT to HOME for dotfiles package
<wael_> how will it get updatrd
<wael_> for me I've always simply symlinked dotfiles to home
<testuser[m]> same but it feels clunky
<wael_> how come
<testuser[m]> kiss pkg will also be clunky but less
<testuser[m]> idk it just feels wrong
<wael_> well it works and it does a good job
<wael_> I don't believe anyone has managed dotfiles with system package
<testuser[m]> local pkg
<testuser[m]> not system pkg
<wael_> local?
<testuser[m]> system pkg would own it to root
<testuser[m]> hmm but making it local pkg would pollute $HOME/var
<wael_> imo one time self-written setup sh script is easier than local package managed dotfiles
<testuser[m]> with kiss pkg u wont need to symlink
<wael_> would it even be symlinked
<testuser[m]> kiss b
<wael_> how will updates be possible then
<wael_> for example modify .profile
<wael_> where do you do the changes
<testuser[m]> in whatever place dotfiles pkg is located
<wael_> which by itself is harder than symlinked since you have to update dotfiles pkg, bump version and files, kiss b, and repeat
<wael_> unless its git repo
<wael_> which takes more space and time than a symlink
<wael_> this is better than pkg
<wael_> maybe hmm
<wael_> but to me I find symlinks easier
lanodan has quit [Quit: WeeChat 3.5]
lanodan has joined #kisslinux
<wael_> oh yeah that method of dotfiles won't work well with custom files
<wael_> for example I have custom etc and qmk configs
<testuser[m]> what
<testuser[m]> thoughts on splitting users/groups from packages? like openntpd and docker would have acct-openntpd and acct-docker with post-install/pre-remove files which add/cleanup group/user
<testuser[m]> and be optional to install
<testuser[m]> or not
<testuser[m]> manual config is OK but this seems better for something like a server
<wael_> what's the point
psydroid has quit [Quit: Bridge terminating on SIGTERM]
testuser[m] has quit [Quit: Bridge terminating on SIGTERM]
ahmadraniri1994[ has quit [Quit: Bridge terminating on SIGTERM]
macslash1[m] has quit [Quit: Bridge terminating on SIGTERM]
wael_ has quit [Quit: Bridge terminating on SIGTERM]
dotkwa[m] has quit [Quit: Bridge terminating on SIGTERM]
iceman[m] has quit [Quit: Bridge terminating on SIGTERM]
virutalmachineus has quit [Quit: Bridge terminating on SIGTERM]
saturn[m] has quit [Quit: Bridge terminating on SIGTERM]
konimex has quit [Quit: Bridge terminating on SIGTERM]
konimex has joined #kisslinux
<Ogromny> Hi
<Ogromny> Why `dnscrypt-proxy` has been dropped :( ?
saturn[m] has joined #kisslinux
virutalmachineus has joined #kisslinux
dotkwa[m] has joined #kisslinux
testuser[m] has joined #kisslinux
wael_ has joined #kisslinux
iceman[m] has joined #kisslinux
psydroid has joined #kisslinux
macslash1[m] has joined #kisslinux
ahmadraniri1994[ has joined #kisslinux
<midfavila> testuser[m] I manage my configs with kiss
<midfavila> i just use the usual install procedure to place them in the tarball where I want them to be
* midfavila shrugs
sereg has joined #kisslinux
chomwitt has quit [*.net *.split]
travankor has quit [*.net *.split]
mtj has quit [*.net *.split]
ghoulpine has quit [*.net *.split]
mtj has joined #kisslinux
chomwitt has joined #kisslinux
ghoulpine has joined #kisslinux
sereg has quit [Ping timeout: 248 seconds]
midfavila has quit [Quit: Leaving.]
midfavila has joined #kisslinux
travankor has joined #kisslinux
rohan has joined #kisslinux
<macslash1[m]> when is kiss going to add support for flatpaks........ :3
ehawkvu has joined #kisslinux
chomwitt has quit [Ping timeout: 268 seconds]
<phoebos> ehawkvu: what did you mean about other implementations of make as system make?
<phoebos> the interest in pdpmake was mostly as a tool to check posix compliance
<ehawkvu> phoebos: the aim of the proposal would be to make switching out which package provides `make` via kiss a relatively painless since all pkgs that req gmake would use the proper command
<ehawkvu> It's not massively important, but a nice to have
rohan has quit [Ping timeout: 260 seconds]
midfavila has quit [Ping timeout: 268 seconds]
rohan has joined #kisslinux
rohan has quit [Ping timeout: 248 seconds]
<phoebos> ie. running `gmake install` in build files? or kiss dynamically switches /use/bin/make to gmake for packages that require it?
GalaxyNova has joined #kisslinux
GalaxyNova has quit [Changing host]
GalaxyNova has joined #kisslinux
midfavila has joined #kisslinux