The current scrollkeeper package has a nasty bug. When you install the scrollkeeper package, you get an initial scrollkeeper database that is the same of the one on the maintainer's system. So, without even having gnome on your system, your system has gnome documentation registered in the database if the maintainer uses gnome on his system.

Second, whenever scrollkeeper-update is run in the postinstall of various gnome packages, it can take a while. This is because scrollkeeper-update goes to the internet to get the scrollkeeper DTD. This DTD is not registered in the system's XML catalog.

A fixed version of scrollkeeper is at http://schoolbak.dyndns.org/~jan/archlinux/scrollkeeper/

Please note that I did not put the database rebuild in the post_upgrade function, and I did not put the XML catalog registration in it. We have to do some juggling with version information in the post_upgrade to decide if post_install should be run or not. I'll leave that for the maintainer. As a workaround, scrollkeeper has to be uninstalled using pacman -Rd scrollkeeper and has to be installed again after that (or run the things in the .install script by hand after upgrading)

The other thing, the .functions script that gets copied is something I'm working on at this moment: I'm trying to place many used things in functions and place them in /usr/share/pacman/functions/$pkgname. These functions can be called from install scripts and PKGBUILD scripts to make these common things a bit more error-safe. As long as Judd doesn't say yes to this, this can be ignored.