@radix023@noauthority.social @Suiseiseki@freesoftwareextremist.com The distro doesn't matter too much, so long as you stick to free software anyway. Just the defaults and the package manager change the experience between them, generally speaking.
When in doubt, there's always the option of #Gentoo, just set ACCEPT_LICENSE="-* @FREE" in your make.conf.
Administered by:
#gentoo
18 posts15 participants0 posts today
KDE is like home to me. Every distro I use, I always have it as a fallback. I used it on Slackware, Gentoo, Debian, Fedora, and Arch, btw. Reminds me of the good times I've had with Windows.
I haven't used it much these days, especially KDE 6 cos I've been on i3 since I think August 2023 but I still have it installed. I come back to it from time to time and yeah it's definitely improving.
https://odysee.com/@BrodieRobertson:5/was-kde-plasma-6-worth-my-time:4
Replied in thread
@iamwaseem As someone who has used #Gentoo in the past, I find this hilarious as well. :D
Perl 版本方案 - Gentoo Wiki
➤ 解決 Perl 版本排序的混亂局面
✤ https://wiki.gentoo.org/wiki/Project:Perl/Version-Scheme
這篇文章解釋了Gentoo系統中 Perl 版本編號方式的獨特性，以及它與上游版本號碼的差異。由於 Perl 使用浮點數排序版本號碼，導致版本排序方式與傳統整數排序不同。Gentoo 採用了一種方案來解碼上游版本號碼，並將其轉換為一致且可預測的格式，方便依賴關係管理和套件版本控制。文章也介紹了 `Gentoo::PerlMod::Version` 工具，可用於進行版本轉換。
+ 終於理解了 Gentoo 中 Perl 版本號碼的規則了，之前一直覺得很奇怪。
+ 這個方案聽起來很複雜，但為了確保系統的穩定性，似乎是必要的。
#Perl #版本控制 #Gentoo
wiki.gentoo.orgProject:Perl/Version-Scheme - Gentoo wiki
In the process of moving over to Gentoo from Arch. Guess I’m entering my customisation arc 
Arch, KDE/Gnome, Systemd are fine. That being said, I’ve been patching PKGBUILDS and customising the kernel more and more as time passes.
Dabbled with Artix, dinit and Hyprland a while ago. Had a blast but lacked the time commitment to set everything up properly; went back to Arch and Gnome.
Goal now is to run that setup on Gentoo, time willing. Going great so far, learning lots 
Been around since early Sabayon as a repository maintainer/developer and stayed in close contact with folks across these projects. This video gets it right. Agree?
Zawsze cieszy, kiedy autorzy paczki zaakceptują trywialną poprawkę, mimo że oczywisty błąd w kodzie w danej chwili ich nie dotyka.
GitHubfix import in test_composite_plotting by mgorny · Pull Request #1011 · lmfit/lmfit-py
Always nice when upstream accepts a trivial fix even though the obvious bug doesn't affect them right now.
GitHubfix import in test_composite_plotting by mgorny · Pull Request #1011 · lmfit/lmfit-py
Najbardziej niepożądany sposób spędzenia soboty: szukanie wszystkich regresji, które twórcom #LLVM udało się wcisnąć tuż przed wydzieleniem gałęzi wydania 21.x, a następnie bisect.
Odpowiedź: 2 poważne regresje w libclc, które psują kompilację i instalację, 2 regresje testów — clang i compiler-rt (w tym pierwszym zmianę szybko cofnięto z głównej gałęzi — po raz drugi, ale nikt nie pomyślał o tym, żeby cofnąć ją z gałęzi wydania), oraz eksperymentalny backend sypiący się na assercie.
Mam nadzieję, że w końcu uda mi się dodać 21.1.0-rc1 z największym kompletem "natychmiastowych" łatek w historii #Gentoo.
Opieka nad LLVM w dystrybucji to jakiś koszmar.
How you don't want to spend your Saturday: figuring out how many regressions #LLVM developers managed to sneak in just before the 21.x branching, and then bisecting them.
The answer: 2 serious regressions breaking libclc build and install, 2 test regressions in clang and compiler-rt respectively (the former quickly reverted on main, for the second time, but nobody thought of backporting), and 1 assertion failure in experimental backend.
Now I really hope I'll manage a clean run for 21.1.0-rc1 with the biggest zero-day LLVM patchset in the history of #Gentoo.
LLVM downstream maintenance is a nightmare.
Your package has 60 thousand tests. You're thinking: "I have good test coverage."
I'm thinking: "half an hour later, a single test will fail. Then I'll spend another half an hour retesting…"
Twoja paczka ma 60 tysięcy testów. Myślisz: "mam dobre pokrycie testami".
Ja myślę: "minie pół godziny, jeden test padnie, i znowu pół godziny testowania…"
Building stuff for #MocaccinoOS is a workflow that starts with a #Gentoo stage3 image. On top of that we grab the fresh #Portage tree. From there we build up all our layers.
Once everything is compiled we test it for breakages, they are rare because we are on Stable tree. Then I give the signal to the Community Repo team and they build against the packages I pushed into staging. Another little test round and we tag a new stable repository. #Docker #Linux
256GB RAM in a home Desktop machine is perfectly normal, right?
Finally maxed out from 64G to 256, max supported for the 2019 board/CPU :D
Guess I should be able to compile qtwebengine with all 48 threads now 
Replied in thread
@wonderfox_dev
Чтоб начать понимать #Gentoo, ставьте сперва #Calculate и переводите её в режим сборки всех пакетов. Потом посидите годик-два, изучите вику, включая гентушную.
Replied in thread
Der #Linux-Kernel hat so 1 Konfiguration „Anzahl der CPU-Kerne, die maximal unterstützt werden sollen“.
Weil der ursprüngliche Rechner (10 Jahre alt) nur 4 Kerne hat, und jeder weitere 8 kiB Kernelspeicher benötigt, habe ich das natürlich aus Optimierungsgründen auf 4 gestellt.
Jetzt habe ich das System auf einem Ryzen gebootet und muss mit 4 Kernen neu kompilieren, ehe alle 48 genutzt werden können 
