#!/usr/bin/make -f

# since paver itself is run as part of the clean process, it generates .pyc files when paver is run.  The the Debian build gets confused by the *.pyc files that exist after cleaning.  Adding -B to python calls prevents that from happening:

override_dh_auto_clean:
	/usr/bin/python -B setup.py clean
	rm -f $(shell find paver/ -name '*.pyc' -printf "%p ")
	rm -rf Paver.egg-info
	find -name '._*' -delete

override_dh_auto_install:
	/usr/bin/python setup.py install --root=$(CURDIR)/debian/python-paver \
	  --install-layout=deb
	mv $(CURDIR)/debian/python-paver/usr/lib/python2.7/dist-packages/paver/docs \
		$(CURDIR)/debian/python-paver/usr/share/doc/python-paver/html
	dh_link /usr/share/javascript/jquery/jquery.js \
	  /usr/share/doc/python-paver/html/_static/jquery.js
	dh_link /usr/share/javascript/jquery/underscore.js \
	  /usr/share/doc/python-paver/html/_static/underscore.js

override_dh_compress:
	dh_compress -i -X.py -X.rst -X.js -X.html

override_dh_installchangelogs:
	dh_installchangelogs ./paver/docs/_sources/changelog.txt

%:
	dh $@ --with python2