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).
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? :-)
Regards,
[0] http://wiki.debian.org/DebianPython/NewPolicy
--
Jonny Lamb, UK [EMAIL PROTECTED]
http://jonnylamb.com GPG: 0x2E039402
signature.asc
Description: Digital signature
------------------------------------------------------------------------- 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
