On Mon, 2008-02-11 at 13:30 +0000, Jonny Lamb wrote:
> On Mon, Feb 11, 2008 at 12:14:26PM +0000, Mark Ellis wrote:
> > Hi Jonny
>
> Hi Mark.
>
> > Debian python policy (which you may well know) says we should build
> > extensions for each version of python in one package called
> > python-{packagename}. This seems relatively easy for packages that use
> > python distutils/setuptools, throw it at cdbs and it does it for you.
> > Our stuff uses pyrex and autotools, so we need some custom stuff in
> > debian/rules to build two trees, then throw in python-central or
> > python-support to bundle it all into the right place.
> >
> > I've had a bit of a go picking rules from other python extensions, got
> > the closest using pyorbit, but not quite successful. Have you had a go
> > at this ?
>
> Amusingly, I'm looking into that right at the moment. I realise I have
> got that pyrex-module-packaging aspect incorrect and will sort it very
> soon. [0] contains some information and links on how to get this
> working. I might move from CDBS to straight debhelper whilst sorting
> this out too. Out of interest, where did you experience this problem?
> Thinking about it now, I suspect it's present with librapi2, librra,
> librtfcomp and (perhaps) pywbxml (the bindings around wbxml2, not the
> pure-python implementation).
>
I guessed you probably would be :)
[0] was the page that depressed me so much, being full of examples of
every kind of build I could imagine except ours. I think moving away
from CDBS is the only way to go at the moment, especially since in the
package docs they explicitly say
"It is not yet capable of handling very complicated situations, like
packages where multiple C or C++ builds with different options and/or
patches are required,"
which seems to me to include python extensions for multiple versions
that dont use setuptools. Sigh.
I originally came across it with pywbxml. I was only packaging this to
host sync-engine 0.11 in my repository, but as soon as I dug a bit
realized that it would indeed affect rapi2, rra, and rtfcomp.
I don't think it's actually that hard to fix, but it does need more
in-depth knowledge of the deb build system than I currently have. I
would definitely recommend a quick look at pyorbit if you want to
investigate, it's the closest to ours I have found.
> On a slightly-related note, I have found a sponsor for my Debian
> packages, and they are being updated in Debian as we speak. This is
> great news, no? :-)
>
This is so cool I have to censor my own response !
Mark
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
SynCE-Devel mailing list
SynCE-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synce-devel
