<acheam>
the one I linked is by cem which makes it 10x better by default
<duplex>
I use that the one by cem
<duplex>
but not just for install
<duplex>
well install of main system
<duplex>
I use it a decent bit
<acheam>
no reason not to package it then
<kyxor>
oh yeah it's smaller, nice
<duplex>
also has a man page which is nice
<acheam>
yes.
<cjw95>
@acheam rust programs I use daily are ripgrep, nushell, starship, exa, alacritty. (cool but not very KISS!)
<acheam>
indeed not very kiss lol
<acheam>
but whatever floats yer boat
<acheam>
I think I'm still the maintainer of exa actually
<kyxor>
I heard that ripgrep is some magic in terms of performace
<acheam>
dilyn: can you please drop all my packages
<duplex>
before I go through the process of packaging it, has anyone already packaged gummiboot?
<acheam>
like, systemd-boot?
<duplex>
yesn't
<acheam>
kyxor: it is very fast
<duplex>
gummiboot was eaten by systemd but alpine still maintains it
<kyxor>
if ripgrep is really that good, we need a good C port then, I am sure C can kick it in the balls if someone cares to optimize
<acheam>
there is the_silver_searcher
<acheam>
but its not as fast
<acheam>
still much faster than grep though
<cjw95>
haha small world. kyxor it blows grep out of the water
<acheam>
there is also ugrep, but its cpp
<acheam>
it is between ripgrep and silver_searcher in speed
<acheam>
I don't think ripgrwp is that much faster than ugrep though
<kyxor>
well, whatever the magic they are using is probably from more efficient algos, or they use advanced hardware features like AVX instruction set
<acheam>
oh nice duplex
<acheam>
might give that a shot at some point
<cjw95>
ooh will have to give ugrep a try
<acheam>
warning: ugrep is big bloat
<acheam>
has archive support and stuff
<duplex>
gummiboot is more KISS than grub imo
<acheam>
grub isnt a very high standard
<duplex>
yeah fair
<acheam>
honestly there are no good bios bootloaders
<duplex>
gummiboot is uefi only sadly
<acheam>
oh
<acheam>
why bother then?
<acheam>
unless your dualbooting, efistub works well I've heard
<duplex>
not for me
<duplex>
my uefi wipes efistubs
<acheam>
oh
<acheam>
bruh
<duplex>
after a couple reboots it's gone
<duplex>
but it still looks for BOOTX64.efi
<duplex>
which gummiboot has
<duplex>
so it works
<duplex>
I could probably fix that though
<duplex>
my uefi is OSS thankfully
Uks2 has quit [Quit: Byee]
Uks2 has joined #kisslinux
<duplex>
I've seen a few things being built with libblkid in the official KISS repo but I can't find a package for it. does anyone know if another package is providing it?
<kyxor>
ok I don't get it, how did dylan get rid of gzip but his package manager is still trying to use gzip to extract tarballs
<kyxor>
ohh I see, wtf
<kyxor>
the package for it now is pigz (gzip) was an alias name
<kyxor>
well that's an easy way to brick a system, is to remove pigz, if you do you can't install most packages anymore, but more important you can't install pigz itself without having pigz
<kyxor>
good that i have backups lol
<kqz>
duplex: util-linux
duplex has quit [Quit: Client closed]
cjw95 has quit [Quit: WeeChat 3.2]
<GalaxyNova>
My ISP's DNS server is down again ;(
<GalaxyNova>
how hard can it be to NOT fuck up the DNS servers every fucking second
<GalaxyNova>
this is the third time this has happened this month
<noocsharp>
use a different dns server
<GalaxyNova>
like google dns? lol
<acheam>
9.9.9.9
<acheam>
very occasionally it had issues
<acheam>
but its privacy respecting at least
<GalaxyNova>
thanks
<noocsharp>
yo, it supports dns over tls
<noocsharp>
thats pretty nice
<noocsharp>
how do i configure my system to use dns over tls by default?
<acheam>
DYLAN: would you be able to clarify the situation with the community repo? if you don't plan on bringing it back could you update the readme/description to point to kiss-community? thanks!
<testuser[m]>
I don't remember properly but i think he decided to limit the official kiss to just the main repo, no more community one
<manjaro-user>
I get an error when building efibootmgr. Are there any known bugs currently for that?
<testuser[m]>
Log ? I think rieto encountered that
<testuser[m]>
Riteo
<manjaro-user>
I'm new to IRC, should I just paste the last few error lines? Does this chat even handle multiple lines? lol
<manjaro-user>
collect2: error: ld returned 1 exit status
<testuser[m]>
idk if people just dont care about fonts or package their own like me
<riteo-laptop>
I'll try dejavu before because I already got the package metadata on hand
<riteo-laptop>
and it works fine
<riteo-laptop>
thanks for the help!
<riteo-laptop>
so apparently that other font is broken
<riteo-laptop>
oh, testuser[m] you're git-bruh?
<testuser[m]>
perhap
<testuser[m]>
s
<riteo-laptop>
I didn't know that! I've seen that name pop up a lot on kiss related projects
<riteo-laptop>
well, I had to change my kernel configuration and now I have to reboot. Since I'll probably still reboot a few times and soon I'll build firefox I think I'll come back later
<riteo-laptop>
cya!
riteo-laptop has quit [Quit: epic font moment]
duplex34 has joined #kisslinux
<duplex34>
do any packages supply gnu-efi-libs or liblzma-devel in kiss or kiss community repo?
<duplex34>
actually it doesn't have to be devel
<dilyn>
all of our packages are -devel packages
<dilyn>
liblzma should be provided by... xz
<dilyn>
i would assume gnu-efi-libs just provides evifar? which is just efivar in the main repo
<manjaro-user>
In the xorg vs wayland section, it talks about using wayland. You have to uncomment kwwinft and comment kwin in the build packages
<GalaxyNova>
manjaro-user: KDE on kiss is not very well supported
<manjaro-user>
ok, I suspected that may be the case
<GalaxyNova>
you should ask dilyn, but personally I would just use sway
<manjaro-user>
I was going to mess with sway regardless
<manjaro-user>
Maybe use kde with sway instead of kwin. Idk
<dilyn>
i wasn't able to get a wayland session to launch for KDE when I was working on it, but wayland support has only gotten better
<dilyn>
however, you'll have to use xwayland (which means you'll need xorg-server) as I don't believe kwin(ft) support a strictly wayland-only session
<manjaro-user>
how is kde support if I just use xorg?
<dilyn>
kwin at least still requires xcb stuff afaik, and kwinft only advertises *better* wayland support, not strictly wayland support
<dilyn>
kde works quite well if you're using just xorg
<dilyn>
although you'll still have to install wayland
<dilyn>
and you might run into a strange issue impacting some people (including me, sometimes) with plasmashell crashing. which I still haven't been able to figure out
<manjaro-user>
so kde basically requires xorg and wayland?
<dilyn>
but you could use something like sowm instead of kwin as your window manager
<dilyn>
yes
<manjaro-user>
If I do end up using kde, I'll likely use sway as my wm
<manjaro-user>
I still love tiling wms. My reason for wanting to use kde is to get everything else
<dilyn>
i don't know if you can switch kwin for sway but if you find that out lmk
<manjaro-user>
I didn't think it would be an issue. I'm building sway right now, so I've yet to try anything
<dilyn>
yeah I'm just not certain how KDE handles compositors; I know you can change the window manager itself that KDE will use, but I think the compositor might be less... selectable. I'll take a poke
<GalaxyNova>
I don't think compositor effects will work if you use sway
<manjaro-user>
So I was checking out the xorg repo
<manjaro-user>
and its own extra repo, and has firefox. Which the core repo extra also has firefox
<manjaro-user>
does that mean they'll conflict or anything like that if I had this xorg repo into my KISS_PATH?
<dilyn>
`kiss` searches for packages like how PATH is searched
<dilyn>
so whatever the first match is for repos in your KISS_PATH, that's the one which will be used
<manjaro-user>
does that mean also that the order I have the repos in my path matters?
<manjaro-user>
And, if so, do I need the xorg extra/comunity first. Since I assume that'll install firefox that works with xorg, and not wayland
claudia has quit [Read error: Connection reset by peer]
claudia has joined #kisslinux
<dilyn>
yes, yes
<manjaro-user>
ok, I moved the xorg paths to be first
<manjaro-user>
does kiss have i3 packaged?
mahmutov has quit [Ping timeout: 258 seconds]
<noocsharp>
see commit 77ad454a7 in community
<noocsharp>
it was packaged, but it looks like it was never added to graveyard
<noocsharp>
you can just retrieve it from there
<noocsharp>
it's no longer in community because it doesn't support wayland
GalaxyNova has quit [Quit: Whoooooshh]
manjaro-user has quit [Remote host closed the connection]
<duplex79>
musl doesn't support multiarch right?
<noocsharp>
i mean it supports multiple architectures
<noocsharp>
what is multiarch?
sad_plan has joined #kisslinux
<sad_plan>
hi
kiedtl|litterbox has quit [Quit: kiedtl|litterbox]
kiedtl|litterbox has joined #kisslinux
claudia has quit [Quit: Leaving]
<duplex79>
noocsharp: "Multiarch is the term being used to refer to the capability of a system to install and run applications of multiple different binary targets on the same system. For example running a i386-linux-gnu application on an amd64-linux-gnu system."
<dilyn>
you would certainly need to rebuild gcc with multilib support
<dilyn>
i can only assume that you would need binutils and musl to change as well? but i'm not entirely certain
<duplex79>
ok so could I safely pretend /usr/lib is the only place libs are going to be?
<dilyn>
all */lib directories are symlinks to /usr/lib
<dilyn>
KISS doesn't support multilib by default, everything is assumed x86_64
<duplex79>
alright good
<dilyn>
so /lib64 -> /usr/lib
<duplex79>
that means I can easily fix clang with gummiboot