existing makepkg.conf

[0rbadvent]

how does extras.sh affect the makepkg.conf settings from repo-ck, linux-ck-bulldozer in one of my cases, does it take ck optimizations into account/?>

[kata198]

extras.sh will overwrite your makepkg.conf file.

I planned originally to make it instead extend -- add a source to the bottom and a /etc/makepkg.d directory where the extra stuff would be added. I didn't implement this yet, but it's not that complicated.

This would have nothing to do with packaegs you are downloading from a repo, it allows you to easily do PGO optimization, etc, all with the best CFLAGS possible. It will compile native for your system, and only affects packaegs you build (see the README, you'll want to use archsrc-getpkg to pull it, then add the single line to the PKGBUILD per the README.)

If you want to be 100% safe that it will not affect any of your custom settings, but sitll take adavntaeg of all the macros, you can do the following:

cd pacman-utils
cat /etc/makepkg.conf >> data/makepkg.conf
sudo cp -f data/makepkg.conf /etc/makepkg.conf

This will cause any overrides you have explicitly set in makepkg.conf to take precedence over any defaults in the pacman-utils extras, but will still allow full use of the explicit macros.

If you've never modified that file, any repos you'e added to pacman.conf or whatever will not be affected and you can just safely overwrite your copy with the pacman-utils copy. Then you'll default to the native CFLAGS and can just use "archsrc-buildpkg [pkgname]" or "aur-buildpkg [pkgname]" to build and insall any package from arch repos or aur repos in one-step. To do PGO, you'll have to add a line, do the profiling yourself (its manual), run "mkgcdatar", and rebuild the package. All described in the README.

Let me know if you have other quesitons, or suggestions for the README to make things more clear!