[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

RE : RE : RE : RE : cctbx debian package


> Install target is not ready to use. We need to figure out how the package
> structure will look like first

In fact the recommended way to package python modules is to use dh_python2 [1]

> > One small difficulty though: the extensions need to be built for all the
> > supported python versions. So we'll need to call the build system
> > several times. And to install each version of the extension at the right
> > place.

> This is already done by the build target. It uses pyversions to determine for
> how many python versions a release has.

if we got a working setup.py all this comes for free ;)

> > By the way, I had a look at the import wrapper they use for loading
> > extensions (boost.python.import_ext) and wrote a few lines about it in
> > the wiki.
> Looks good. I was thinking again about dependencies on small python packages.
> Maybe it's really best to do just one python package "python-cctbx" with all modules
> and all extensions? Else I don't have any clue how to build multiple packages
> with one setup.py. Do you?

We need to follow the python-policy [3], python-foo binary packages for each module.

yes you "just" need to use the dh_install infrasctructure to split into n-binary packages [2].

See you

[1] http://wiki.debian.org/Python/TransitionToDHPython2
[2] http://man.he.net/man1/dh_install
[3] http://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html#s-package_names

Reply to: