Hi Jonny
Following on from my fun and games with the opensync python plugin, I
was looking into debian python packages and policy (I need to get out
more).
It looks like we've been following much the same ideas lately, but I was
hoping you'd had some bright ideas I hadn't yet :) I'm going to run
through what I've found out for the list, someone else may know some
good stuff.
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 ?
Someone also asked me a little while ago about supporting different
python versions in relation to ubuntu, John Carr maybe ?
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
