Daniel has a point, that the @VAR@ strings need to be protected against configure expansion
We thus introduce quoting again here, but using only double quotes seems a safer choice though:
This variable is used as
sed -e '$(pkgconf_SUBST)'
so quote matching does not happen the way it seems at first glance

On FC5 and above rpmbuil will run brp on all python files that
generates the .pyc and .pyo files. The spec file currently accounts
for that and explicitly ignores them. However, brp is not run by
FC4's version of rpmbuild and so we need to explicitly create them
using "touch". This seems like the most harmless way to get things
working rather than trying to build in conditionals that check whether
we are on FC4.