Hello,

> [2] I have recently converted phonon and its backends will follow soon.

I have already switched a couple of kde-req and kde-std packages to qt-kde-
team/2/* [1]. So far so good. Checklist:

1) Build-Depend on pkg-kde-tools (>= 0.11).

2) s,/usr/share/pkg-kde-tools/qt-kde-team/1,/usr/share/pkg-kde-tools/qt-kde-
team/2,.

3) Replace cdbs variables and hooks with override_{dh_command} targets. Avoid 
using dhmk hooks in debian/rules directly (for the sake of clarity and 
consistency).

4) In most cases call overriden commands via $(overriden_command) in the 
override targets (unless its effect is not desirable). $(overriden_command) 
expands to the full original command line of the overriden command including 
additional arguments added by dh addons and "dh" variable (if any).

5) Do not forget to specify --dbg-package manually (either via 
"override_dh_strip:\n\t$(overriden_command) --dbg-package=pkg" (recommended as 
it's less verbose in the build log output) or "dh --dbg-package=pkg". Thats 
needed because cdbs detects dbg package automatically while qt-kde-team/2/* 
does not (and should not).

6) library-packages.mk was rewritten and variable names were changed. Change 
them accordingly in debian/rules.

7) Test if the package is actually acted upon before doing anything non-
debhelper related with it in the overrides (esp. if it's arch: all). That's 
needed due to the different set of packages operated on during binary and 
binary-arch builds. You can use if [ -d debian/pkgname ] (faster) or if [ -n 
"$(filter pkgname,$(shell dh_listpackages))" ] or similar techniques for this.

[1] phonon, phonon-backend-*, soprano, akonadi, polkit-qt-1, qimageblitz ...

-- 
Modestas Vainius <mo...@debian.org>

Attachment: signature.asc
Description: This is a digitally signed message part.

--
http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-talk

Reply via email to