04:35 <testuser[m]> Hi

04:44 <GalaxyNova> hi

05:48 <wael_> Hi

06:20 <GalaxyNova> anyway to continue on my rant from earlier, standards are definetly needed to have a useable computing ecosystem

06:20 <GalaxyNova> but top-down designed standards are bad

06:21 <GalaxyNova> imo standards should be decided uppon by the implementors

06:22 <GalaxyNova> midfavila

06:22 <GalaxyNova> i think they're offline

06:50 <macslash1[m]> Meow

06:59 <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

06:59 <testuser[m]> How can u have an impl before a standard is made

07:00 <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

08:43 <testuser[m]> has anyone thought of managing dotfiles with kiss

08:44 <testuser[m]> like setting KISS_ROOT to HOME for dotfiles package

08:45 <wael_> how will it get updatrd

08:45 <wael_> for me I've always simply symlinked dotfiles to home

08:45 <testuser[m]> same but it feels clunky

08:45 <wael_> how come

08:45 <testuser[m]> kiss pkg will also be clunky but less

08:45 <testuser[m]> idk it just feels wrong

08:45 <wael_> well it works and it does a good job

08:46 <wael_> I don't believe anyone has managed dotfiles with system package

08:46 <testuser[m]> local pkg

08:46 <testuser[m]> not system pkg

08:46 <wael_> local?

08:46 <testuser[m]> system pkg would own it to root

08:47 <testuser[m]> hmm but making it local pkg would pollute $HOME/var

08:47 <wael_> imo one time self-written setup sh script is easier than local package managed dotfiles

08:47 <testuser[m]> with kiss pkg u wont need to symlink

08:47 <wael_> would it even be symlinked

08:47 <testuser[m]> kiss b

08:47 <wael_> how will updates be possible then

08:47 <wael_> for example modify .profile

08:47 <wael_> where do you do the changes

08:47 <testuser[m]> in whatever place dotfiles pkg is located

08:48 <wael_> which by itself is harder than symlinked since you have to update dotfiles pkg, bump version and files, kiss b, and repeat

08:48 <wael_> unless its git repo

08:48 <wael_> which takes more space and time than a symlink

08:54 <testuser[m]> https://www.atlassian.com/git/tutorials/dotfiles

08:55 <wael_> this is better than pkg

08:55 <wael_> maybe hmm

08:55 <wael_> but to me I find symlinks easier

09:26 <wael_> oh yeah that method of dotfiles won't work well with custom files

09:26 <wael_> for example I have custom etc and qmk configs

09:46 <testuser[m]> what

10:12 <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

10:12 <testuser[m]> and be optional to install

10:12 <testuser[m]> or not

10:13 <testuser[m]> manual config is OK but this seems better for something like a server

10:21 <wael_> what's the point

11:42 <Ogromny> Hi

11:42 <Ogromny> Why `dnscrypt-proxy` has been dropped :( ?

13:08 <midfavila> testuser[m] I manage my configs with kiss

13:08 <midfavila> i just use the usual install procedure to place them in the tarball where I want them to be

21:01 <macslash1[m]> when is kiss going to add support for flatpaks........ :3

21:54 <phoebos> ehawkvu: what did you mean about other implementations of make as system make?

21:54 <phoebos> the interest in pdpmake was mostly as a tool to check posix compliance

22:03 <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

22:04 <ehawkvu> It's not massively important, but a nice to have

22:40 <phoebos> ie. running `gmake install` in build files? or kiss dynamically switches /use/bin/make to gmake for packages that require it?