On Wed, 18 Jul 2012 17:42:07 +0200
Radostan Riedel <[email protected]> wrote:

> On Wed, 18. Jul 15:15, Picca Frédéric-Emmanuel wrote:
> > In that case we should work with the cbf maintainer and see if the
> > python binding could be package on its own, do
> > 1) check that both cbf python binding are equivalent
> CCTBX provides a more recent version of cbflib. But the python bindings are
> building with the provided setup.py. It creates a _pycbf.so extension. 

you should fill also a bug for the new version :)

> > 2) found the real homepage of the official pycbf which seems to be part of 
> > cbflib.
> Could not find anything. Looks like this bindings were developed upstream or 
> at
> least contributed to upstream.
> > 2) fill a bug against cbflib package to add the a python-pycbf package. (it 
> > seems thaht pycbf is available from cbflib source package).
> Just did that: Bug#681997
> > 4) do not build pycbf from cctbx
> I'll write a patch to skip the build.

can you provide a compile option for this until we solved the libcbf package 
issue.
so it will be easy for use to switch from the bundeled pycbf and the official 
pycbf.

> > 5) one of you sumerize all this in the wiki once we are clear about this 
> > problem ?
> Already on my todo list.

:), it would be nice to put the relevant [[DebianBug:xxx]] in the wiki.

Cheers

Fred

-- 
GPG public key 4096R/4696E015 2011-02-14
    fingerprint = E92E 7E6E 9E9D A6B1 AA31  39DC 5632 906F 4696 E015
uid  Picca Frédéric-Emmanuel <[email protected]>

GPG public key 1024D/A59B1171 2009-08-11
    fingerprint = 1688 A3D6 F0BD E4DF 2E6B  06AA B6A9 BA6A A59B 1171
uid  Picca Frédéric-Emmanuel <[email protected]>


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: http://lists.debian.org/[email protected]

Reply via email to