illiliti has quit [Remote host closed the connection]
<virutalmachineus>
Just switch UEFI command line and it feels great, suckless to the max.
<virutalmachineus>
* Just switch ed to UEFI command
<wael_>
What
fitrh has joined #kisslinux
fitrh has quit [Read error: Connection reset by peer]
fitrh has joined #kisslinux
<testuser[m]>
..yes well it got out of date when i had to go to prison again...and being in a jail cell for a few years i could not keep it updated..and now there is too much incompatibility to try to update it...so i just use it like it is except with a couple of mods....
<wael_>
shouldn't KISS_FORCE also force build?
<testuser[m]>
Prompt
<wael_>
TIL
<wael_>
wait that doesnt exactly force a build
<wael_>
that just allows the implicit dependencies to get installed
<wael_>
if a package relies on a dependency that only relies on that one package, would it be fair to bundle it with the package?
<testuser[m]>
no
<wael_>
it must be unbundled?
<wael_>
and be a seperate package?
<testuser[m]>
ye
<wael_>
why is that
<testuser[m]>
no
<testuser[m]>
just don't
<testuser[m]>
u can make it a make dep and link static if u want
<wael_>
yea but why
<testuser[m]>
cuz it's hacky
<wael_>
but since the dependency is only needed by 1 package it makes sense to bundle no?
<testuser[m]>
N O
<wael_>
wah
<macslash1[m]>
Lol
<macslash1[m]>
I mean like if that dep is used in a diff program later down the road then it could cause issues
illiliti has joined #kisslinux
<wael_>
hence why i said specifically for one pacakge
<wael_>
if another needed it then it gets unbundled
<testuser[m]>
Wat does bundling save
<testuser[m]>
nothing
<wael_>
1 less dependency
<wael_>
''''''''''''''''dependency'''''''''''''''''''' in this case
<testuser[m]>
you're just fooling yourself then
<wael_>
that is exactly my goal
sad_plan has joined #kisslinux
<sad_plan>
wael_: but each time you build that package, you build 2 packages. which takes longer, and will put a larger strain on peoples systems
<wael_>
true true
<wael_>
but then look at freetype-harfbuzz lmoahjo
<sad_plan>
theres a reason for it. you force build harfbuzz with freetype support, and vice versa. if we hadnt done that, users would have to explicitly rebuild freetype and harfbuzz
<sad_plan>
but sure, I see your point
<wael_>
you literally proved my point wrong wtf
<testuser[m]>
Just modify kiss to return pkg count after dividing by 10
<sad_plan>
what did you expect? :p
<sad_plan>
^ lol
<wael_>
time to make own package manager so that 29 core packages are bundled as one meta core package
<sad_plan>
or build things statically linked, and 40 packages will get to like 4 packages. in the case of statically linked tinyx, st glazier sx sxhkd
<wael_>
what the fart
<sad_plan>
alot of libX stuff you know
<sad_plan>
aswell as xcb stuff for glazier and sxhkd
<sad_plan>
its a library which glazier uses. also from same place
<wael_>
danmn
<testuser[m]>
wael: you're gonna bundle it aren't yoi
<wael_>
bundlwe what
<aelspire>
Hi, I'm new to KISS linux and currently I'm trying to bloat my installation to replicate my workflow from void linux before I could think what can I remove. I like fish shell and I noticed that any completions are removed from official packages. I would like to re-add them and not sure how to do this with less friction. I guess this might be possible with KISS_HOOKS. Anyone can provide me some directions how this can be done or fork is the only way?
<wael_>
sway and foot are the only notable programs with removed fish completions
<testuser[m]>
aelspire: they're removed in the package build files themselves so you'll have to fork pkgs
<testuser[m]>
Idk why they're removed
<testuser[m]>
What do u need those for anyway they exist for like 3 packages
<aelspire>
well, fish can generate completions from man pages, but I guess the ones provided in packages are better. So this is tiny problem for me
<aelspire>
but I noticed this completion remowals and it irked my OCD a little
<wael_>
oh yeah fish completions are removed in the default tarball i believe
<aelspire>
pre-build KISS_HOOK's second arg is just a directory where package will be builded? yes? no access to build script from repo?
<wael_>
a kiss_hook is applied on packages when building the tarball, which removes all completion for shells
<wael_>
aelspire: ?
<aelspire>
there is pre-build KISS_HOOK and I hoped that it has access to build script from package
<aelspire>
so it can modify build instruction for packages
<wael_>
i mean you technically can do that but its quite difficult
<wael_>
its only 2 notable packages that explicitly have completion disabled
<aelspire>
$ rg fish
<aelspire>
community/community/swayidle/build
<aelspire>
community/community/swaylock/build
<aelspire>
8: -Dfish-completions=false \
<aelspire>
9: -Dfish-completions=false \
<aelspire>
21: -Dfish-completions=false \
<aelspire>
repo/wayland/sway-no-seat/build
<aelspire>
repo/wayland/sway/build
<aelspire>
18: -Dfish-completions=false \
<aelspire>
repo/wayland/sway-tiny/build
<aelspire>
20: -Dfish-completions=false \
<aelspire>
repo/wayland/foot-pgo/build
<aelspire>
yes, it look like there are only a few packages with fish removed
<wael_>
i wouldnt believe that sway and foot are packages that need completion
<aelspire>
so fork is the way
<wael_>
maybe swayidle or swaylock would benefit
<aelspire>
ok, cool thanks for help
<aelspire>
forking few packages is no problem
<aelspire>
if doing this via hook is too much trouble
<wael_>
you can simply make a repo and symlink all files except the build file
<testuser[m]>
So bad
<wael_>
Whart
<aelspire>
I'm quite impressed with kiss-community. gcc is at version 12.2.0 while void still has 10.2.1 and updating to 12.x still looks like a lot of work. KUDOS
<wael_>
this is simply because its less maintenance than void
<aelspire>
sometimes I think that void took too big bite, too
<wael_>
void has maybe 8 architectures and maybe thousands of packages that are all binary, also with the fact that packages take very long times to update
<aelspire>
they literally need 3x developers they have
<wael_>
eg llvm is still version 12 and prs have been opening for 13, closed, 14, closed 15, and the dudes working on those prs are not getting ANY support by maintainers
<aelspire>
and on Arch I use some packages from AUR, void has everything in main repo
<aelspire>
insane amount of work needed to maintain this
<wael_>
yep
<saturn[m]>
testuser: is installing microG on lineageos as simple as just installing the apks and installing from there?
<sad_plan>
no
<sad_plan>
microg has to be installed from recovery, or via magisk
<sad_plan>
unless they changed it
<sad_plan>
iirc microg has to be system app
<saturn[m]>
oh, i saw some apks there: didn’t know that
<macslash1[m]>
aelspire I mean, dylan was right about repos becoming too big to handle, kiss repos are tiny and yet accomplish most of what people need because most packages are quite niche on those kinds of distros
<saturn[m]>
never really touched android much so i don’t have an idea on how to do this lol
<sad_plan>
havent used it in ages, so it mightve gotten changed, but I doubt it
<wael_>
macslash1: its also extremely easy to fork and maintain yourself
<macslash1[m]>
Also true
<macslash1[m]>
Easy to customize things to your liking even if it may not work for other people
<testuser[m]>
aelspire: void has 1000x more maintenance burden
<testuser[m]>
saturn: u can't install microg on lineage to do anything useful
<testuser[m]>
It needs signature spoofing so you need some other rom or lineage4microg
<macslash1[m]>
Void has many things, its a shame because its a fantastic distro but its just impossible to maintain
<aelspire>
macslash1: yes I think so too, so I'm trying kiss. I tried void and alpine before but for void I don't like its package system (you fork the main repo for xbps-src and merge your packages to it) and the packages are little too old, as I need newer C++ for work. And in alpine I didn't like OpenRC. Deamontools-alikes are the best!
<testuser[m]>
Also KISS is less "tested" so you might get pkg build breaks at times
<testuser[m]>
Like we usually don't do full rebuild of repo+community on gcc ipdate
<testuser[m]>
For testing
<wael_>
kiss userbase is very very very very very very very very very very very very very tiny no time to test
<saturn[m]>
testuser[m]: oh damn, what should i use instead?
<wael_>
testuser suggested another rom
<saturn[m]>
oh
<macslash1[m]>
The users are the testers, no real need to test too much cus you can literally just contact the maintainer directly and they will fix it or lose their ownership
<wael_>
testuser is the tester
<testuser[m]>
What do you need microg for
<sad_plan>
I suggest grapeneOS or calyx, maybe divestos aswell. in that order
<testuser[m]>
Most stuff can be used in browser
<testuser[m]>
I needed just location part of microg that works without sig spoofing so i made a quick hacky fork
<saturn[m]>
what’s the benefit of using microg btw
<saturn[m]>
what will i lose if i dont use it
<testuser[m]>
nothing
<testuser[m]>
Other than network location
<saturn[m]>
so wifi and stuff will work and i can just install apps like normal
<wael_>
testuser[m]: has the pr been merged yet tho
<aelspire>
wael_: But I also think that breakages are smaller problem. On void package to merge into main branch must be perfect and cause no breakage. If kiss-community allow imperfect merges, one person will fix one thing, next person will fix other thing, and in result there will be incremental improvements to the repo, and with time there will be no breakages in used packages.
<wael_>
so true
<testuser[m]>
saturn: depends on what apps
<saturn[m]>
testuser[m]: i probably will just use youtube and get the aliucord apk, element too
<saturn[m]>
and some minor customizing with nova launcher
<testuser[m]>
All those will work
<testuser[m]>
Use newpipe for ewwtube
<saturn[m]>
alright
<saturn[m]>
should i use lineageos’ recovery.img or no need
<sad_plan>
use the zip file, and use twrp to flash it. just remember to flash the twrp zip aswell afterwards, so you keep twrp
ella-0 has quit [Ping timeout: 260 seconds]
<macslash1[m]>
Configured a kernel by myself for the 2nd time
<macslash1[m]>
What r the odds ive messed up
<testuser[m]>
68.34%
<macslash1[m]>
Yea fair enough
<sad_plan>
do an all-no config, its way more fun. also a great learning experience
<sad_plan>
I did it earlier, it was great, but also abit frustrating, as things broke, and I didnt know why
<testuser[m]>
What use was the learning experience then
<testuser[m]>
lol
<sad_plan>
figuring out why things break, and whats needed and not
<macslash1[m]>
sad_plan: a.... what?
<macslash1[m]>
So just turn everything off anf turn on stuff a bit at a time lol
<sad_plan>
I started with explicitly only enabling things I knew my system would not boot without, and when It booted, I turned stuff on as I notived I needed them
<sad_plan>
macslash1[m]: exacly. however, the kernel doesnt have a all-no config option, so you have a to create a new config, then do some sed magic to remove everything effiecnelty
<wael_>
@sad_plan but why allnoconfig
<wael_>
wouldnt everything straight up break
<testuser[m]>
So you can spend even more time configuring
<sad_plan>
i doesnt exist
<wael_>
mfw minimal config
<wael_>
I shall try it out
<sad_plan>
yes, what size is your kernel anyway? I had a pretty minimal kernel to begin with, and shaved off 1mb
<sad_plan>
its not at 6mb. this is with -O2. Im down to 5mb with -Os if I wanted to
<sad_plan>
s/not/now/
<wael_>
idk probably 13mb
<wael_>
honestly I just want performance
<sad_plan>
well thers probably some performance to gain there. removing stuff thats not used, and choosing options that will improve the performance
<sad_plan>
have a look at dotslashlinux. it has some guides on choosing the options which will benefit you. aswell as things that might not matter, which can then be removed
<testuser[m]>
What does it do
<wael_>
whatsca dotslashlibux
<sad_plan>
its a website. it goes through the kernel configuration process, and points out what different configs do, and wether or not you might need them. I know most of this is sortof outlined in the help section for earch config, but it still helps shed abit more light on some of them
<wael_>
thanks
<wael_>
maybe I'll look at TkG, Xanmod kernel patches too
<sad_plan>
perhaps. isnt the zen kernel also supposed to be more performant? I seem to recall that. never used it. I use lts
<wael_>
Idk
<sad_plan>
its worth a read anyway, if performance is what youre after
sad_plan has quit [Quit: nyaa~]
<macslash1[m]>
Zen kernel is apparently good for home pcs
<macslash1[m]>
A bunch of kernel hack stuff try it ig
<saturn[m]>
macslash1[m]: you most likely wouldn’t even experience a difference
<macslash1[m]>
Might do on a very low end system
<saturn[m]>
how low end
<macslash1[m]>
I imagine compiling for speed on a diff pc then moving it over might squeeze out a bit more
<macslash1[m]>
Not sure, ig u would have to test that
<macslash1[m]>
Maybe good for a rasp pi or smth
<saturn[m]>
macslash1[m]: rasp pis aren’t so low end
<macslash1[m]>
Depends theres quite a few models
sad_plan has joined #kisslinux
phinxy has joined #kisslinux
sam_sepi0l has joined #kisslinux
stjohn has joined #kisslinux
aelspire has left #kisslinux [#kisslinux]
<macslash1[m]>
How would I move kiss out of /mnt while keeping my system intact until kiss boots
<wael_>
you can't keep your system intact while replacing the entire root
<wael_>
Wait
<wael_>
Have a look at switch_root(8)
<illiliti>
no
<illiliti>
switch_root will remove old root
<illiliti>
it essentially does rm -rf /
<illiliti>
make sure you don't lose anything
fdkol has quit [Ping timeout: 260 seconds]
<illiliti>
and you need to be pid 1. otherwise switch_root won't work
<macslash1[m]>
illiliti I dont have anything on my system anyway
<macslash1[m]>
Lol
<macslash1[m]>
But like im confused on how I use it, do I use switch_root on /mnt/?
<sad_plan>
macslash1[m]: you are running a kiss install, and have a new kiss install mounted to /mnt? is that correct?
<macslash1[m]>
Yea
<sad_plan>
I dont see any reason for you to no just move the files you want into / though. Ive done stuff like that all the time. unpack a tarball, and move /usr from /mnt to /. no issues
<sad_plan>
unless youve done something that will explicitly break stuff in your current install, I dont see any reason for it to not work
<macslash1[m]>
Fair
<macslash1[m]>
Ill just remove /bin last and it should be fine
<sad_plan>
if you know your stuff in /mnt works, add it to patch, so if your / breaks, things still work
<sad_plan>
what did you do in /mnt that you couldnt do in your running machine?
<sad_plan>
also, dont move things from /mnt, copy it instead
<macslash1[m]>
Kk
<sad_plan>
s/patch/path/
<macslash1[m]>
Okay i found a better way by just going into a live usb lmao
<sad_plan>
thats also a way to do it :p
sad_plan has quit [Quit: nyaa~]
phinxy has quit [Quit: WeeChat 3.5-dev]
phinxy has joined #kisslinux
fdkol has joined #kisslinux
phinxy has quit [Quit: WeeChat 3.5-dev]
phinxy has joined #kisslinux
<illiliti>
mold might soon become non-free software :(
<illiliti>
we gotta, unfortunately, remove it from repos when/if that happens