[SCM] Free Firewire Audio Drivers (ffado.org) packaging branch, master, updated. debian/2.0.0+svn1806-1-10-ga1a93ce
Jonas Smedegaard
jonas at jones.dk
Tue Apr 20 15:50:08 UTC 2010
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)
>>> +debian/tmp/usr/lib/python*
>>> 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
>
> /usr/lib/python2.5/site-packages/ffado/
>
>
>and
>
> http://www.debian.org/doc/packaging-manuals/python-policy/ch-python.html#s-paths
>
>says
>
> 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,
>
>
> http://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html
>
>says
>
> 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20100420/3464b49d/attachment.pgp>
More information about the pkg-multimedia-maintainers
mailing list