Jppy: comments to the current jppy

[Nicholas Piper]

Norbert,

On Sun, 21 May 2006, Norbert Preining wrote:
> On Son, 21 Mai 2006, Nicholas Piper wrote:

> >  * It wasn't clear that jppy depends on libpisock 0.12, and that
> >    jpilot MUST be also compiled against that version if you want to
> >    use the jpilot plugin. (Now I've added a message to the wiki to say
> >    this.)

> Yup, I have installed all the pilot-link packages from
> Debian/experimental which is 0.12.0-pre4.

> Only one strange thing, but probably a bug in the packaging: The
> pisock.py (and friends) are installed on Debian into /usr/lib/python/
> where there are *not* found by jppy. I linked them into
> /usr/lib/python2.3/site-packages/ and of you go.

This is a change to previous packaging yes. Maybe it's a bug, please
email Ludovic Rousseau <rousseau at debian.org> and let him know.

> >  * build-depends wasn't complete. (I've now added libpisock-dev,
> >    python-egenix-mx-base-dev, thanks.)

> Did you add a versioned conflict on the packages in experimental,
> together with the Binary Deps on these?

The binary depends line for jppy itself is:

 Depends: libatk1.0-0 (>= 1.9.0), libc6 (>= 2.3.6-6), libcairo2 (>=
 1.0.2-2), libfontconfig1 (>= 2.3.0), libglib2.0-0 (>= 2.10.0),
 libgtk2.0-0 (>= 2.8.0), libpango1.0-0 (>= 1.12.1), libpisock9,
 libx11-6, libxcursor1 (>> 1.1.2), libxext6, libxi6, libxinerama1,
 libxrandr2, libxrender1 (>= 1:0.9.0.2), python2.3 (>= 2.3),
 python-reportlab, python, python-egenix-mxdatetime

While for the jpilot plugins:

 Depends: libatk1.0-0 (>= 1.9.0), libc6 (>= 2.3.6-6), libcairo2 (>=
 1.0.2-2), libfontconfig1 (>= 2.3.0), libglib2.0-0 (>= 2.10.0),
 libgtk2.0-0 (>= 2.8.0), libpango1.0-0 (>= 1.12.1), libpisock9,
 libx11-6, libxcursor1 (>> 1.1.2), libxext6, libxi6, libxinerama1,
 libxrandr2, libxrender1 (>= 1:0.9.0.2), python2.3 (>= 2.3), jpilot

For build-depends:

 debhelper (>= 4.0.0), scons, swig, libgtk2.0-dev, python-gtk2-dev,
 bison, libpisock-dev, python-egenix-mx-base-dev

I can add libpisock-dev to be >= 0.11.8-0.12.0-pre4-4

Is that all you mean, or are there further changes you're suggesting?
Do you think I should Conflict with all current versions of jpilot in
debian? I'm not sure how to do that; I don't know the version number
they'll use when they switch to libpisock9. I will ask Ludovic
Rousseau by CCing him on this mail.

Ludovic: My package 'jppy-jpilot-plugins" will only work if jpilot is
linked with libpisock9. Currently that means people have to recompile
their own jpilot (not a real problem at this point I think,
considering the technical level of jppy.) It would be nice if apt
could warn them about this somehow?

 Nick

-- 
Nick Piper, Developer, LogicaCMG           http://www.nickpiper.co.uk/
GPG Encrypted mail welcome!                             1024D/3ED8B27F
Choose life. Be Vegan :-) Please reduce needless cruelty + suffering !