<wael_>
<Ellowee[m]> "Who was doing the ubuntu..." <- doesn't exist
<wael_>
according to kiss-find atlesat
<wael_>
theres alpine kernel packages tho lol
<Ellowee[m]>
Oh?
<midfavila>
>packaging your kernel
<neptune_>
ubuntu kernel?
<wael_>
yes that can be quite useful
<midfavila>
goodness gracious me oh my
<midfavila>
how far you've fallen, wael_
<midfavila>
to the stocks with you
<wael_>
What?
<Ellowee[m]>
neptune_: Someone mentioned packaging it here some time ago and I really am getting tired of configuring manually and missing a lot of features
<neptune_>
oh cool
<wael_>
just look at ubuntu kernel .config
<wael_>
midfavila: do you know any good X email client?
<midfavila>
xmh
<midfavila>
:D
<wael_>
is that a real thing or are you fucking with me
<midfavila>
look it up and find out nerd
<midfavila>
= w
<midfavila>
=
<wael_>
ok is there another good one other than xmh that looks reasonably good
<wael_>
i said it doesn't exist according to kiss-find
soliwilos has quit [Remote host closed the connection]
<sad_plan>
midfavila: whats wrong with letting kiss build your kernel? I do that, and I find it way more usefull imo
<wael_>
>i fucking commented on the damn pr
<sad_plan>
ah, well its because its not merged yet
<sad_plan>
lol
<sad_plan>
s/kiss build your kernel/kiss manage your kernel/
midfavila-tab has joined #kisslinux
trunc88 has joined #kisslinux
<oak[m]>
Does anyone know how youre supposed to install mkiss? It doesn't provide any tarballs
<sad_plan>
I dont see any reason why you couldnt just use a regular kiss-tarball and just use mkiss repo instead
<wael_>
because mkiss has an entirely different core/ than to kisslinux
<wael_>
which makes it pretty hard to transform to mkiss
<sad_plan>
I know, but seeing as we have the alternative system, switching things out is rather simple
<wael_>
switching out the entire coreutils
<wael_>
well sure i guess
<wael_>
mkiss uses gnu coreutils btw
<sad_plan>
unless mkiss uses llvm, just switching repos should be trivial. even then, you can still just use konimex's old kiss-llvm to convert to llvm
<sad_plan>
I dont see why that matters. just build coreutils, then switch to coreutils
<sad_plan>
just like you switch to toybox. btw, how did that go? did you get things up and running sufficently?
soliwilos has joined #kisslinux
<oak[m]>
<sad_plan> "I know, but seeing as we have..." <- I dont even know what i should be switching out though
<sad_plan>
to coreutils, and w/e else mkiss have, that kiss does not
<sad_plan>
it seems mkiss uses coreutils instead of busybox, so you would build coreutils, among other things, then just use the alternative system to switch to coretuils
<sad_plan>
why not just use regular kiss?
<wael_>
mkiss has tons of packages and has gnome
<wael_>
using bash as the build shebang too
<sad_plan>
I noticed
<wael_>
and many packages that need depends are simply missing the 'depends' file
<sad_plan>
sloppy
<sad_plan>
also from my point of view, it mostly looks like dartmans personal repo
<wael_>
honestly if she's doing all of that with regular kiss why even use kiss
<sad_plan>
source based distro though. still better than genpoo as testuser refer to it as :p
<wael_>
the fucking sheer amount of packages are insane
<sad_plan>
I noticed. I was looking in core, and I was in awe of the amount of pacakges in just core alone..
<wael_>
this person is managing to maintain god knows how many packages better than kiss maintainers probably
<sad_plan>
maybe
<wael_>
I take my words back
<wael_>
theres probably more packages in mkiss/core than there are in community
<oak[m]>
<sad_plan> "why not just use regular kiss?" <- I am right now, I want multilib though. Flatpak hasnt been very reliable for me
<wael_>
I literally maintain a multilib repo for gkiss and im using flatpak right now
<wael_>
with working sound and it works really great
<sad_plan>
oak[m]: then get multilib. wael_ has the repo for it as he mentioned.
<oak[m]>
Using proton with the flatpak breaks most games for me
<sad_plan>
core has 198 packages it seems. which is just ludicrus
<oak[m]>
sad_plan: I would have to switch to gkiss
<wael_>
mate
<wael_>
I can make a lib32-musl
<sad_plan>
you can. I dont play much games anymore, and if I do, Ive instead used a chroot for artix, or just dualboot artix
<wael_>
probably a whole lot fucking easier than glibc
<oak[m]>
wael_: Thats not how it worjs
<oak[m]>
Works
<wael_>
glibc lib32 required by multilib gcc required by glibc lib32
<wael_>
oak[m]: you're not the one who decides
<oak[m]>
Musl doesnt have multilib
<wael_>
gcc lib32 is required
<oak[m]>
Yes
<wael_>
oak[m]: multilib in this context is a library or program to lib32
<wael_>
aka 32-bit
<wael_>
aka ia32
<wael_>
AFAIK GCC needs a glibc lib32 header for multilib
<oak[m]>
sad_plan: Chroot hasnt been reliable for me too
<oak[m]>
I really just want native
<sad_plan>
I get that. native is obviously best
<wael_>
oak[m]: If you want to know if you can use multilib with musl