Maemo users may be able to build their own QtWebKit2.0 debian packages.
Created attachment 55287 [details] Patch with proposed debianization
How much of this is specific to Maemo vs. generic Debian packaging ? Will this work on a desktop Debian environment ?
(In reply to comment #2) > How much of this is specific to Maemo vs. generic Debian packaging ? Will this > work on a desktop Debian environment ? And how to handle Maemo6 packaging when that is going to be needed?
I asked exactly both these questions to Belem in person. (In reply to comment #2) > And how to handle Maemo6 packaging when that is going to be needed? According to him, the short term plan is to upstream the maemo5 debianization (WebKit/qt/debian/fremantle), but it'd become in a soon future general for maemo, so WebKit/qt/debian/maemo/ maybe by DEB_BUILD_OPTIONS="{fremantle,harmatan}, XXX" > How much of this is specific to Maemo vs. generic Debian packaging ? Will this > work on a desktop Debian environment ? I will let Belem to answer that. But I agree that we should make it so that all debian based distros could use the debianization infra we provide here to create their packages. IMO it should even support patching by allowing using quilt, so they could easily patch it for shipping.
(In reply to comment #2) > How much of this is specific to Maemo vs. generic Debian packaging ? Will this > work on a desktop Debian environment ? It will work on debian with small changes, such as installation path will be different and some dependencies have different package name.
(In reply to comment #3) > (In reply to comment #2) > > How much of this is specific to Maemo vs. generic Debian packaging ? Will this > > work on a desktop Debian environment ? > > And how to handle Maemo6 packaging when that is going to be needed? I think it will work without changes for harmattan.
If we see this work being useful for all Debian based distro's in the near future, i would vote for putting it under WebKit/qt/debian/ (without any sub directory below) - even if in its current status it has been only tested with Fremantle.
(In reply to comment #7) > If we see this work being useful for all Debian based distro's in the near > future, i would vote for putting it under WebKit/qt/debian/ (without any sub > directory below) - even if in its current status it has been only tested with > Fremantle. I think the packages are going to be debian distro specific, I don't expect there to be much sharing. The control files are going to differ, so are the .install and changelogs. However I also think that WebKit/qt/debian/fremantle is the right location for the fremantle specific files (or maemo5, whichever you like :)
Comment on attachment 55287 [details] Patch with proposed debianization The files look fine to me, but please move them to WebKit/qt/debian/fremantle or maemo5.
use maemo5 please
Created attachment 55862 [details] Updated patch with the requested changes
Comment on attachment 55862 [details] Updated patch with the requested changes WebKit/qt/debian/maemo5/control:30 + QtWebKit provides a Web browser engine that makes it easy to embed content I would say Web contents and editing engine (I think that is what the site says) WebKit/qt/debian/maemo5/control:33 + Package: libqt4-webkit-dev I wonder if we should rename this as it is now a separate project
As discussed on the phone, we're going to use git-buildpackage and separate package repositories for the actual packaging.
(In reply to comment #13) > As discussed on the phone, we're going to use git-buildpackage and separate package repositories for the actual packaging. Simon, are you saying that this build files should not be up-streamed ?
(In reply to comment #14) > (In reply to comment #13) > > As discussed on the phone, we're going to use git-buildpackage and separate package repositories for the actual packaging. > > Simon, are you saying that this build files should not be up-streamed ? Yep
Comment on attachment 55862 [details] Updated patch with the requested changes Clearing review, as the packaging files are maintained separately now.