Local version newer than repo version.

Question

I got sick of using Enlightenment 16.7.1 (newest in the repo) so I altered the PKGBUILD and made 16.7.2-1 and now I get this whenever I use pacman..
:: enlightenment: local version (0.16.7.2-1) is newer than repo version (0.16.7.1-2
Is there a "right" way to make that just.. go away?

Answer 1

Yes, it is very easy.
1. Put your pkgbuilds in a heirarchical structure, much like in abs. I have the following structure for mine.
/var/abs/local/
/var/abs/local/amavisd-new
/var/abs/local/ltsp-utils
/var/abs/local/mod_ruby
/var/abs/local/php
/var/abs/local/postfix
/var/abs/local/webalizer
The pkgbuilds and the related files are in their respective folders..
2. Move the binary packages that are resultant from building the packages to a folder of your choosing. Like /home/eliott/public_html/archlinux/binary-packages/ for example.
3.
gensync /var/abs/local/ /home/eliott/public_html/archlinux/binary-packages/cactus_repo.db.tar.gz
The first part of the db.tar.gz target is the name of the repository that you would put in brackets in pacman.conf.
4. Put rule in pacman.conf
If you wan't it to override what is in the archlinux repos, then put it first.
[cactus_repo]
Server = file:///home/eliott/public_html/archlinux/binary-packages
#Server = http://cactuswax.net/~eliott/archlinux/binary-packages
The first server is if the repo is on the same machine. The second one, commented out, is if it is on a different machine. This is very useful if you have alot of servers, and want to centrally manage package deployment.
Now, everytime you update a package or add a new one, you can just rerun the gensync command above, and it will rebuild the repo list for you.