Hello from Debian and Ubuntu =)
Dmitrijs Ledkovs
I'm from Debian Crosswire Packaging Team. We package sword related
stuff in Debian and Ubuntu. We also are running daily-builds,
developer-preview and stable ppa with sword softwares.
I have recently managed to build a debian package for sword SWIG
python bindings. I now hope to package BPBible for Debian/Ubuntu.
As a first step I have create a stub launchpad.net/bpbible project.
This project on launchpad is to facilitate our team's packaging
efforts. Similar projects are set-up for sword, bibletime and xiphos.
All of these are under ubrella project "crosswire" on launchpad.
What do we use launchpad for? We will have automatic bzr import of
bpbible svn trunk. Debian packaging will derive / use that, since our
team has standardised on packaging using bzr branches.
All the rest of launchpad project page *clearly* states that upstream
website, upstream code hosting, upstream bug-tracking, upstream
translations and upstream support is done elsewhere not on launchpad.
That is here on google-code / google-groups combo.
I hope you are ok with this. I hope to start packaging BPBible as soon
as I sort out migrating our current packages to sword-1.6.2.
You can contact Debian Crosswire Packaging team via open mailing list
pkg-cross...@lists.alioth.debian.org.
With best regards,
Dmitrijs Ledkovs
Jonathan Morgan
We are certainly happy for BPBible to be packaged. However, something you should probably know before starting is that the upcoming BPBible 0.5 is built on a different rendering engine (wxWebConnect). A few things about this:
1. wxWebConnect is based on XULRunner. I recall there were discussions in the past about the fact that Ubuntu preferred to support WebKit rather than XULRunner because of the difficulty of keeping XULRunner secure and patched.
2. wxWebConnect is currently somewhat fragile and based on a particular version of XULRunner (1.9.2). I know it doesn't work with 1.9.1, and I could almost guarantee it won't work with 2.0.
3. BPBible is based on a forked and somewhat heavily patched version of wxWebConnect. I recall concerns being expressed about packaging patched versions of products. The intention is that eventually patches make their way to the upstream Kirix release (and the project lead has indicated about some of them that they will be integrated into the next version), but since they do not have a repository visible to the public and are not very communicative I do not know when that release will be or which changes would be in it.
4. BPBible relies on SWIG bindings for wxWebConnect written by me that are not very nicely packaged.
I have actually compiled my version of wxWebConnect on the latest version of Ubuntu and run it, so I know it is possible, but each of these things could be a barrier to packaging it for Ubuntu.
Jon
Dmitrijs Ledkovs
> Hi Dmitrijis,
>
> We are certainly happy for BPBible to be packaged. However, something you
> should probably know before starting is that the upcoming BPBible 0.5 is
> built on a different rendering engine (wxWebConnect). A few things about
> this:
Thanks a lot for the head up =) I hope to at least package 0.4.7.
> 1. wxWebConnect is based on XULRunner. I recall there were discussions in
> the past about the fact that Ubuntu preferred to support WebKit rather than
> XULRunner because of the difficulty of keeping XULRunner secure and patched.
>
Xiphos is using XULRunner. I'm quite up-to-date about XULRunner policy
in Ubuntu and I'm on good terms with Ubuntu Mozilla Team.
The general policy is: new mayor xulrunners will be updated
post-release. You can expect Lucid to be upgraded to xulrunner-2.0,
2.1 and probably 2.3 in the future. Ported apps will be upgraded,
those that are not ported will be dropped.
> 2. wxWebConnect is currently somewhat fragile and based on a particular
> version of XULRunner (1.9.2). I know it doesn't work with 1.9.1, and I
> could almost guarantee it won't work with 2.0.
>
2.0 will be default in Natty and 1.9.2 is currently preffered-default
in all prior releases.
I can help testing with 2.0.
> 3. BPBible is based on a forked and somewhat heavily patched version of
> wxWebConnect. I recall concerns being expressed about packaging patched
> versions of products. The intention is that eventually patches make their
> way to the upstream Kirix release (and the project lead has indicated about
> some of them that they will be integrated into the next version), but since
> they do not have a repository visible to the public and are not very
> communicative I do not know when that release will be or which changes would
> be in it.
>
Plain wonderful. Can you provide this patches? If they are good enough
I can help pushing them to Debian/Ubuntu if they are high quality and
"do-the-right-thing".
When you say "BPBIble is based on a forked wxWebConnect" will it not
build, run or both on "vanilla" version?
> 4. BPBible relies on SWIG bindings for wxWebConnect written by me that are
> not very nicely packaged.
>
Please provide SWIG bindings and we will try to push them to Ubuntu/Debian =)
> I have actually compiled my version of wxWebConnect on the latest version of
> Ubuntu and run it, so I know it is possible, but each of these things could
> be a barrier to packaging it for Ubuntu.
>
Where abouts? Is it in a ppa?
Jonathan Morgan
On 2 December 2010 01:50, Jonathan Morgan <jonmm...@gmail.com> wrote:Thanks a lot for the head up =) I hope to at least package 0.4.7.
> Hi Dmitrijis,
>
> We are certainly happy for BPBible to be packaged. However, something you
> should probably know before starting is that the upcoming BPBible 0.5 is
> built on a different rendering engine (wxWebConnect). A few things about
> this:
Xiphos is using XULRunner. I'm quite up-to-date about XULRunner policy
> 1. wxWebConnect is based on XULRunner. I recall there were discussions in
> the past about the fact that Ubuntu preferred to support WebKit rather than
> XULRunner because of the difficulty of keeping XULRunner secure and patched.
>
in Ubuntu and I'm on good terms with Ubuntu Mozilla Team.
The general policy is: new mayor xulrunners will be updated
post-release. You can expect Lucid to be upgraded to xulrunner-2.0,
2.1 and probably 2.3 in the future. Ported apps will be upgraded,
those that are not ported will be dropped.
2.0 will be default in Natty and 1.9.2 is currently preffered-default
> 2. wxWebConnect is currently somewhat fragile and based on a particular
> version of XULRunner (1.9.2). I know it doesn't work with 1.9.1, and I
> could almost guarantee it won't work with 2.0.
>
in all prior releases.
I can help testing with 2.0.
I'm happy to do testing, and having upgraded it from 1.8.0 to 1.9.2 earlier in the year I probably know most of the places that will need changing. But there will be a few core changes needed to make it really support multiple versions of XULRunner well, and while I have made proposals for how to do this on the Kirix forums, I haven't actually had time to implement them.
Plain wonderful. Can you provide this patches? If they are good enough
> 3. BPBible is based on a forked and somewhat heavily patched version of
> wxWebConnect. I recall concerns being expressed about packaging patched
> versions of products. The intention is that eventually patches make their
> way to the upstream Kirix release (and the project lead has indicated about
> some of them that they will be integrated into the next version), but since
> they do not have a repository visible to the public and are not very
> communicative I do not know when that release will be or which changes would
> be in it.
>
I can help pushing them to Debian/Ubuntu if they are high quality and
"do-the-right-thing".
I maintain all my changes in a Github repository (https://github.com/jonmmorgan/wxwebconnect).
As for doing the right thing and being of high quality, they do the right thing for us, but some of them are at best beta level or experimental (I was intending to fix some of the loose ends before releasing 0.5).
When you say "BPBIble is based on a forked wxWebConnect" will it not
build, run or both on "vanilla" version?
Being Python, it will probably "build" but will definitely not run. Actually, now I think about it the Python bindings won't build without the forked version, since they expose methods in the forked one.
Please provide SWIG bindings and we will try to push them to Ubuntu/Debian =)
> 4. BPBible relies on SWIG bindings for wxWebConnect written by me that are
> not very nicely packaged.
>
The bindings are at https://github.com/jonmmorgan/pywebconnect, but they don't even have a build script with them. I have a somewhat hacked version of the wxPython setup.py that I use, but since I had to make a collection of random changes to it on every platform I built on I thought it not really ready for inclusion.
Where abouts? Is it in a ppa?
> I have actually compiled my version of wxWebConnect on the latest version of
> Ubuntu and run it, so I know it is possible, but each of these things could
> be a barrier to packaging it for Ubuntu.
>
No, just on my home computer. I was just trying to make it work at all.
Jon