acheam 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/1JloNFppFE8
ashln has joined #kisslinux
<ashln> I'm going to be shoving a small computer into a freezer in the near future, and would like to load it with a distribution in which very little can go wrong. I'd like to remove everything non-essential up to and including the package manager. Is kiss a good starting point, or should I look elsewhere?
<phoebos> something like nix is probably more reliable, but less understandable
<illiliti> openwrt
<illiliti> alpine
<illiliti> kiss is acceptable too tbh, but you would have to compile everything from source, including kernel
humaid_ has joined #kisslinux
<humaid_> Hi
<humaid_> testuser: I noticed the latest chromium binary(v100) doesn't crash like v96-99 (aw, snap..etc). But the pdf viewer is smoother on the previous ones...do you know why?
<jslick> ashin: maybe oasis linux
<illiliti> no idea about pdf viewer though
denshi has joined #kisslinux
denshi has quit [Client Quit]
ioraff has joined #kisslinux
<noocsharp> ashln: go wrong in what sense?
<testuser[m]> Hi
<illiliti> hi
<noocsharp> o/
<ioraff> illiliti: perhaps we should make a meson symlink for muon, like how there's a ninja symlink for samurai.
<illiliti> > cli compatibility with meson. muon has different flags, subcommands, etc., and should not be renamed/symlinked to meson.
<ioraff> if the build files are written to adhere to a strict (i.e. muon-compliant) meson spec, I don't see how it matters.
<ioraff> I suppose in use outside of the repository
<illiliti> cli interface isn't in meson spec
<illiliti> there's no standard to adhere in this case
<ioraff> ah
<testuser[m]> meson has more stuff like coverage and pgo support so it wouldn't make sense for general use
<illiliti> even if we do symlink, it would not work anyway. for example, meson provides install target in build.ninja file, while muon rightfully don't and so on
* illiliti need to resume work on muon...
<illiliti> there were some problems with subprojects in sway* packages before i postponed my work
<illiliti> also another problem is that mesa depends on llvm which doesn't have pkg-config since 2011
<illiliti> meson has special handling of llvm in order to fix this
<illiliti> which is insane
ioraff has quit [Quit: ioraff]
<testuser[m]> illiliti: couldn't we ship our own pc file for lolvm
<illiliti> yeah, i think we can
<illiliti> still i would like to reduce the amount of patches and workarounds
<illiliti> there are not too many of them atm, most of them related to convoluted gnome module
illiliti has quit [Quit: later]
humaid_ has quit [Ping timeout: 255 seconds]
denshi has joined #kisslinux
denshi has quit [Quit: denshi]
amogussy has joined #kisslinux
amogussy has quit [Client Quit]
Houne has joined #kisslinux
soliwilos has quit [Remote host closed the connection]
soliwilos has joined #kisslinux
soliwilos has quit [Remote host closed the connection]
soliwilos has joined #kisslinux
<phoebos> not sure "tag support" is the right phrase
dilyn has joined #kisslinux
<dilyn> acheam: noocsharp: correct, nobody asked me :v
<dilyn> I've been a :ghost:
dilyn has quit [Quit: Connection closed]
<omanom> I like that drew frames it all as a targeted attack on him and sourcehut
ella-0_ has joined #kisslinux
ella-0 has quit [Read error: Connection reset by peer]
<noocsharp> i don't think he's saying its targetted, but just that google is being negligent with the amount of requests that they send
<omanom> It is the wording he chooses to use which makes it sound like SourceHut is the only one being affected by this -- "Google has been DDoSing SourceHut", "a year later I am still being DDoSed by Google", "having our little-fish service DoS’d by a 1.38 trillion dollar company"
ashln has left #kisslinux [#kisslinux]
<testuser[m]> Maybe it’s because crypto actually needs the advanced features and correctness that Rust provides, while language doesn’t matter for most of your basic CRUD jobs so people use JS or whatever
Houne has quit [Read error: Connection reset by peer]
ejjdhfjsu has joined #kisslinux
soliwilos has quit [Quit: zzz]
soliwilos has joined #kisslinux
ioraff has joined #kisslinux
rohan has joined #kisslinux
<rohan> man
<rohan> is just me or kiss and CPU not work well together
<rohan> i tried do install the same package with pip in kiss and fedora
<rohan> and fedora is much faster than kiss
<phoebos> has anyone had a problem building firefox, #include_next <gdk/gdkx.h> not found
<phoebos> i think i've had this before but can't remember what i did
<ioraff> rohan: I don't think pip is very CPU-dependent
<ioraff> phoebos: not lately. log?
<rohan> ioraff: so who maybe is the problem for this?
<ioraff> are you saying pip is faster or the package you installed with pip is faster?
<rohan> the package
<ioraff> what package?
<rohan> is line 15 minutes with matplotlib to install
<rohan> and fedora is like 2 minutes
<rohan> i using a r7 3700u
<ioraff> I would guess fedora makes use of some multithreading, which our pip apparently does not. in any case, have a look at matplotlib+numpy in my personal repository (old/ folder), which link against a kiss-suitable openblas
<rohan> so kiss not handle multithreading?
<omanom> you should try to rule out differences in how python is compiled and installed first
<phoebos> are you sure the difference isn't from network caching or something
dilyn has joined #kisslinux
<dilyn> "KISS" isn't what doesn't support multithreading -- if you enabled it in your kernel, you have SMT
<dilyn> rohan: what's your CPU clocked at in KISS?
<dilyn> you might be using a bad governor
<rohan> my governor is performance
<ioraff> fedora may just be installing prebuilt wheels, whereas our pip needs to do some compilation
<rohan> yeah
<rohan> thats a resonable anwser
<ioraff> this line: "Using legacy 'setup.py install' for matplotlib, since package 'wheel' is not installed." would seem to indicate that
<rohan> yeah thats why too long
<rohan> and it seems to compile
<rohan> when starts compilation oguri seems slow
<ioraff> try installing wheel first
oldtopman has quit [Remote host closed the connection]
oldtopman has joined #kisslinux
rohan has quit [Ping timeout: 258 seconds]
humaid_ has joined #kisslinux
illiliti has joined #kisslinux
<humaid_> illiliti: I see. pdf viewer is usable but sluggish a bit. v100 chromium doesn't snap, so I'm okay with it.
<humaid_> (because we don't have intel core i9999999 with 9999999gb ram to compile chromium all day
<humaid_> ^ haha.
<cem> rohan: yeah there are some optimisations that should be done in kiss
<cem> A couple of months ago I rewrote the dependency fixing
<cem> Makes a huge difference
<cem> In terms of both CPU usage and the time it requires to fix dependencies
humaid_ has quit [Remote host closed the connection]
<cem> I now re-read the conversation, and realised that it was not related to the package manager :)
<cem> But still putting it out there, heh
<dilyn> cem! :D
<cem> Hey dilyn!