You are not logged in.
Hi,
pacman/makepkg.conf/zst compression level 20 works on single core only. Level 19 is multicore and much faster. Is there any specific reason that Arch ships with this exotic (ultra) level? Not sure if there's something wrong on my side though (4 core/16GB RAM).
Last edited by Maniaxx (2024-02-13 09:27:19)
sys2064
Offline
https://bbs.archlinux.org/viewtopic.php … 0#p2150180
Edit: https://gitlab.archlinux.org/archlinux/ … c4ddadb85a
Edit more: https://gitlab.archlinux.org/archlinux/ … ote_148233
Last edited by seth (2024-02-12 23:07:27)
Online
Thanks. So it's some kind of "conformity" or "following upstream" thing then i guess.
sys2064
Offline
It's following https://archlinux.org/packages/extra/any/devtools/ - and I fail to make up a reason for that.
devtools is for package maintainers, ie. explicitly targeted at sharing built packages - unlike what 99% of Joe AUR-user does.
For local builds (typical end-user installing AUR stuff on a single system), just disable compression (.tar suffix) altogether.
It's just wasting CPU, time (and now also RAM) first compressing and then decompressing the package for the (immediate) installation.
You also probably don't want to build debug enabled (except if you feel you might have to debug that package)
The system-wide configuration file is found in /etc/makepkg.conf. Individual options can be overridden (or added to) on a per-user basis in $XDG_CONFIG_HOME/pacman/makepkg.conf or ~/.makepkg.conf, with the former taking priority.
Fix it there.
Online
With the move to tracking devtools makepkg.conf, in pacman 6.0.2-9, now debug packages are built and installed by default, which I don't want cluttering up my system.
I also found that some AUR packages fail to build with the 'lto' option enabled. This seems to be linked to the compiler used for various components of the package.
As above, overriding the OPTIONS values in $XDG_CONFIG_HOME/pacman/makepkg.conf is the clean solution.
Last edited by emulti (2024-02-15 10:14:16)
Offline
Online