On Tue, Apr 20, 2010 at 05:17:34PM +0200, Adrian Knoth wrote:
On Tue, Apr 20, 2010 at 04:46:11PM +0200, Jonas Smedegaard wrote:

   Include python site-packages for ffado-mixer (Closes: #578499)
support/xdg/ffado.org-ffadomixer.desktop usr/share/applications/

This looks wrong: Python modules should be packaged separately,
following Debian Python Policy.

We're talking about





  Public Python modules not handled by python-central or python-support
  must be installed in the system Python modules directory,
  /usr/lib/pythonX.Y/dist-packages for python2.6 and later, and
  /usr/lib/pythonX.Y/site-packages for python2.5 and earlier.

We could probably call python-support in the rules file, if it's not
done automagically by cdbs. ;)

I certainly recommend to use one of thos Python install systems, not try to outsmart them.

Doing so with CDBS goes roughly like this:

 * Include CDBS class python-module.mk
 * Declare above CDBS inclusions which Python install system to use
 * Add proper ${python:*} variables to control file
* Follow documentation of the chosen Python install system on what other hints is needed
 * Update build dependencies

In addition,



  Python packages are directories containing at least a __init__.py,
  other modules, extensions and packages (A package in the Python sense is
  unrelated to a Debian package)

From these lines, I don't think we're required to package this very ffado-specific python support module into a separate package, it probably won't make any sense at all. (there is nobody else relying on it)

The debconf package also places a debconf.py in site-packages.

Fair enough - if not a module then it need not be packaged separately, but packaging still needs to follow Python Policy.

 - Jonas

* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: Digital signature

pkg-multimedia-maintainers mailing list

Reply via email to