ALHP provides v3 compilation for all official packages; but we remain with Chaotic-AUR packages not optimized.
Could v3/v4 compilation be added to Chaotic-AUR?
ALHP provides v3 compilation for all official packages; but we remain with Chaotic-AUR packages not optimized.
Could v3/v4 compilation be added to Chaotic-AUR?
This is a great question, unfortunately there isnāt really a way to answer it concisely and still get all the points across in a condensed way.
This would indeed have potential to boost performance on new hardware up to ~10% (sometimes more) in application-specific situations. More realistically, the difference tends to be smaller when averaged out. Thereās a huge showstopping problem, though: compatibility!
We make the responsible choice to allow as many people as possible to use the packages we provide. For now (at least), weāre keeping parity with Arch, which means anyone can use anything. I regularly see people here on the forum, Matrix, and on Telegram using Chaotic-AUR with older hardware.
As you can tell in my profile, in one of my PCs Iām using the first CPU to support v3 (Haswell), and itās still way more than plenty powerful enough to do its job without v3 optimizations. Should the CPU before it (3770k), with nearly no performance delta (2%) not be allowed to work? What about the generations before, which can overclock to (or beyond) the same performance level?
One of the entire reasons to use a repo for precompiled binaries is that older hardware can work fine, but compile times often suck and waste power on a global scale. This is only amplified by frequent rebuilds. This means if we stop supporting older hardware, and thereās no effective replacement, then thereās an environmental impact due to suddenly not serving those who could (or did) otherwise benefit.
This has historically been a tricky thing to address and even approach in the Linux world, because thereās always someone running older hardware. Who are we to determine what hardware people are allowed to useāassuming itās performing effectively? My personal view is that everyone deserves a right to use modern software on functional hardware without artificial or arbitrary restriction.
There are other good distros that exist and exclusively target newer instruction sets by design. CachyOS is a great example of that. Unfortunately, not everyone can get compatible hardware, and Chaotic-AUR supports more distros than Garuda. So here we sit.
Thereās a discussion specific to Arch here:
There is relevant info here:
You can see here that we are currently (and will continue) to use LTO, and some other reasonable alterations:
I think itās technically feasible in the vaguely-near future to consider v3 builds on the new infrastructure. Thereās many other higher-priority things to be sorted out first though.
@dr460nf1r3 is the one who ultimately decides when (if) that change could happen. Ideally for Garuda, we could continue to provide the same packages as before, but optionally enable the alternative repo if the hardware supports it.
The problem with that is that we would very suddenly be building twice as many things, and the repository size for mirrors would double to a whopping ~150gb minimum! Thatās a big deal. The only potential half-solution I see would be primarily providing v3/4 builds via R2 CDN, but I much prefer having our existing mirrors available. I can and would purchase a new disk to upgrade my mirror, but certainly not everyone can. Iām also rather sure not all mirrors could effectively keep a synced state with double the downstream bandwidth requirements.
I just installed librewolf and noticed chaotic repo is behind aur for days for this package. Is there a specific reason?
yay -Sii librewolf ī² ā
Repositorium : chaotic-aur
Name : librewolf
Version : 128.0.3-1
yay -Sii aur/librewolf ī² ā
Repository : aur
Name : librewolf
Version : 128.0.3-2
The most limiting factor as of now is resources. 1) disk space as outlined and 2) CPU power - though we are basically building 2 Chaotic-AUR repos currently due to the infra 4.0 test phase I can see this becoming a less limiting factor in the future, when 4.0 is live (itās a lot more efficient due to different reasons). From a technical point of view itās absolutely possible with the new infra without having to run multiple instances of build tools.
Expecting to add this soon
can you add this terminal please : ptyxis https://aur.archlinux.org/packages/ptyxis
https://aur.archlinux.org/packages/linux-amd
linux-amd finally got a new maintainer and is now updated to 6.10
in chaotic I still see 6.8
thank you
Hey there! cowfortune is broken just for me or everyone else?
It tries to find directory /usr/share/cows
but it doesnāt exist. Probably, it just -ay for the end of cowsay is missing, I guess.
Thanks for reporting this, xiota fixed it by clearing the cache, which lingered after the maintainer changed. The new version was made available shortly after this post.
Funny bug indeed, thatās on the maintainer to fix! I opened an issue upstream:
can you add the new default gnome pdf viewer Papers please : AUR (en) - papers
and this upcoming terminal : AUR (en) - ghostty-git
Why do we need terminals in the beta stage in Chaotic-AUR?
We already have enough to do with KDE/Plasma, Nvidia and GNOME ā¦
i like betas
But your avatar doesnāt look like a beta version, or am I wrong?
I can change that if you like.
Are you asking me out dude
Well it also exists to provide preview versions of software, the reason why it features bleeding edge stuff such as mesa-git or firefox-nightlies. But, given we canāt compile it anyways itās not possible anyways.
@houssem.kochat9 have you even read the description, or used this before?
Ghostty is currently in a closed beta phase and can only be installed by members of the beta. Once Ghostty is open sourced the source URL will be updated
As always, you can sum it up better, that was what I read too.