My iniial reaction was that packer should handle both cases.
1. A list of packages from official packagage database
2. A mixed list of AUR targets and packages from official packagage database
For example I tried to do
and get an
Code: Select all
error: failed to commit transaction (conflicting files)
aalib: /usr/bin/aafire exists in filesystem
aalib: /usr/bin/aainfo exists in filesystem
aalib: /usr/bin/aalib-config exists in filesystem
aalib: /usr/bin/aasavefont exists in filesystem
aalib: /usr/bin/aatest exists in filesystem
aalib: /usr/include/aalib.h exists in filesystem
aalib: /usr/lib/libaa.a exists in filesystem
aalib: /usr/lib/libaa.so exists in filesystem
aalib: /usr/lib/libaa.so.1 exists in filesystem
aalib: /usr/lib/libaa.so.1.0.4 exists in filesystem
aalib: /usr/share/aclocal/aalib.m4 exists in filesystem
with makesfs(pacman -Sw) I dont get any indication that aalib is already installed
on the other hand packer2 doesnt correctly uninstall pacman dependencies if issued only official packagages
But this I would like to fix in packer2'
perhaps uninstalling with pacman -Rs in packer2 line 395
Code: Select all
if [[ $pacmanpackages ]]; then runasroot $PACMAN "${PACOPTS[@]}" -Rs "${pacmanpackages[@]}"; fi
A quick test I made would suggest it works
Of course some error handling as you suggested before squashing is great
Sim what are your take on this, pros and cons?
.