FHS location for locally-compiled bytecode (was: FHS location for Python libraries as locally-compiled bytecode)

2008-07-04 Thread Ben Finney
A little while ago on debian-python, we discussed the location of system files that are executable bytecode, created by package management tools at install time, and how to comply with th FHS. Ben Finney <[EMAIL PROTECTED]> writes: > Josselin Mouette <[EMAIL PROTECTED]> writes: > > > As for the

Re: dh_pycentral and dh_pysupport clash

2008-07-04 Thread Ben Finney
Ben Finney <[EMAIL PROTECTED]> writes: > = > .PHONY: install > install: build > dh --with python_central install --before pysupport > dh --with python_central install --after pysupport > > .PHONY: binary-indep > binary-indep: build install > dh --with python_central bi

dh_pycentral and dh_pysupport clash

2008-07-04 Thread Ben Finney
Howdy all, I'm having a conflict between 'dh_pycentral' and 'dh_pysupport' that I can't see how to resolve. Case study: 'python-minimock' http://ftp.debian.org/debian/pool/main/p/python-minimock/python-minimock_0.8-4.dsc> Currently (in 0.8-4) the 'debian/rules' has the following targets of inte