You are not logged in.
Pages: 1
I've been using Packer to manage my AUR packages. I know the majority will say AUR package managers are rubbish, quit using them, etc, etc, and maybe I will eventually. But for now I've been using Packer for its ease of use when it comes to updating my packages. I can -Syu --auronly and find out if any of them need updated. That being said, with the release of AUR4 does this mean that none of my packages installed from the previous AUR will be updated and "packer -Syu --auronly" will always say there is nothing to update? I've been reading up on the AUR and how it all works to try and better understand it, and will continue to read up on it but just wanted some clarification on the matter. I've currently got 20 AUR packages installed and am not sure if I need to reinstall them via the AUR4, if packer will eventually pull from AUR4, etc, etc.
Thanks for any and all input.
Last edited by GunnDawg (2015-06-10 03:07:44)
Offline
I'm not sure exactly how packer works, but assuming it uses the API or scrapes the site then there should be no problems for it. The move to git is primarily for how maintainers manage/submit the packages.
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
So the end user doing the downloading of said packages will notice minimal differences between AUR and AUR4? Also aftering doing some more reading I'm seeing that people are suggesting cower over packer if you are infact using an AUR package manager. Anyone care to chime in on that?
Offline
cower > *
Offline
cower-12.tar.gz ... FAILED (unknown public key 1EB2638FF56C0C53)
==> ERROR: One or more PGP signatures could not be verified!
Have not seen this happen when building an AUR package before.
Offline
Search: this has been covered a lot...
Offline
disregard. I've fixed it.
Offline
Pages: 1