[aur-general] force flag usage

[Xavier]

I believe this thread concerns the community repo as well, so please 
have a look:
http://archlinux.org/pipermail/arch-dev-public/2008-May/006243.html

However there is something to figure out about how the community repo is 
built : packages need to be built with makepkg >= 3.1.2, and added to 
the database with repo-add >= 3.1.2

In the meantime, the following two steps can still be done:
* reevaluate if the flag is still needed. I would guess if it hasn't 
needed a 'force' since before the last ISO, then we should be fine.
* convert the old force=y syntax to new options=('force') syntax

Note that the community database itself doesn't contain a single FORCE 
flag, which means all the force flag below are not used at all. If 
nobody even noticed / complained, they probably can be removed.

community/devel/pygtk-docs/PKGBUILD:options=('docs' 'force')
community/devel/fox-legacy/PKGBUILD:options=('!libtool' 'force')
community/daemons/gnump3d/PKGBUILD:force=y
community/daemons/nas/PKGBUILD:force=y
community/x11/compiz-core/PKGBUILD:options=(!libtool !emptydir force)
community/x11/compiz-decorator-gtk/PKGBUILD:options=(!libtool force)
community/games/etracer/PKGBUILD:options=('force')
community/lib/libjingle/PKGBUILD:force=y
community/lib/colorer/PKGBUILD:options=(force)
community/multimedia/alsa-plugins/PKGBUILD:force=y
community/multimedia/xmms2/PKGBUILD:force=y
community/modules/nokia_dku2/PKGBUILD:force=y
community/science/qgis/PKGBUILD:options=('force')
community/office/fbreader/PKGBUILD:force=y
community/network/pyaim/PKGBUILD:force=y
community/network/dokuwiki/PKGBUILD:force=y
community/network/pyicq/PKGBUILD:force=y
community/network/checkgmail/PKGBUILD:options=(force)
community/network/gnunet-gtk/PKGBUILD:force=y
community/network/gnunet/PKGBUILD:options=('!libtool' '!makeflags' 'force')