You are not logged in.
I think you can customize the PKGBUILDs to add / remove features
--include-X --disable-Ybut it would indeed involve quite a bit editing.
Yeah, that's what I was getting at: without the umbrella solution of USE flags, the time and effort required to edit and proof-read each script seems overwhelming. With Arch it's more practical to edit PKGBUILDs for particular apps that contain unwanted features, rather than trying to rebuild an entire system during an update.
Offline
Wouldn't
yaourt -Sb $(pacman -Qq)
work?
You could also set up aliases:
echo "alias pacbuild="yaourt -Sb $(pacman -Qq)"" >> ~/.bashrc
Or you could add a --noconfirm flag to either to build automatically:
yaourt -Sb $(pacman -Qq) --noconfirm
echo "alias pacbuild="yaourt -Sb $(pacman -Qq) --noconfirm"" >> ~/.bashrc
And to build for your CPU's native arch, edit /etc/makepkg.conf
...
#########################################################################
# ARCHITECTURE, COMPILE FLAGS
#########################################################################
#
CARCH="x86_64"
CHOST="x86_64-unknown-linux-gnu"
#-- Compiler and Linker Flags
# -march (or -mcpu) builds exclusively for an architecture
# -mtune optimizes for an architecture, but builds for whole processor family
CFLAGS="-march=x86-64 -mtune=native -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2"
CXXFLAGS="-march=x86-64 -mtune=native -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2"
LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu"
#-- Make Flags: change this for DistCC/SMP systems
MAKEFLAGS="-j3" # Number of cores in your CPU + 1
...
Offline