Arch Linux

ksnw

Member

Registered: 2023-02-26

Posts: 6

pacman makepkg.conf different from pacman source tree?

The makepkg.conf[https://gitlab.archlinux.org/pacman/pacman/-/blob/master/etc/makepkg.conf.in#L93] file in pacman source tree has OPTIONS line as the following:

OPTIONS=(strip docs libtool staticlibs emptydirs zipman purge !debug !lto !autodeps)

but when I remove my local /etc/makepkg.conf and reinstall pacman, the same line looks like this:

OPTIONS=(strip docs !libtool !staticlibs emptydirs zipman purge debug lto)

Who modifies it?

BS86

Member

Registered: 2022-11-03

Posts: 29

Re: pacman makepkg.conf different from pacman source tree?

You are looking at the repo where pacman is developed.

That is what is in the actual pacman package:
https://gitlab.archlinux.org/archlinux/ … type=heads

ksnw

Member

Registered: 2023-02-26

Posts: 6

Re: pacman makepkg.conf different from pacman source tree?

thanks!

Curious though - I can understand the patching work for third party upstream packages, but for something like pacman which Arch team have total control, why not just edit the source?

Last edited by ksnw (2024-03-08 19:28:17)

ayekat

Member

Registered: 2011-01-17

Posts: 1,599

Re: pacman makepkg.conf different from pacman source tree?

While Pacman is developed mainly for (and by developers of) Arch Linux, it is not exclusively developed for Arch Linux.

So what is considered sensible defaults may differ between upstream Pacman development and downstream Arch Linux package maintenance (even if it were done by the same people).

---

pkgs │ hacks │ cfg │ blag