Packaging Development KDEPIM Versions for N900 Fremantle

[Volker Krause]

On Friday 26 August 2011 10:11:23 Andre Heinecke wrote:
> Hi,
> 
> I'm taking this discussion from kde-mobile-users to kde-mobile as i am now
> starting the trunk packager again for the new targets.

great, thanks!

> Initial Targets will be:
> Attica-0.2.0 (unchanged)
> automoc 0.9.88 (unchanged)
> akonadi master
> Soprano master (will be broken) see above

Soprano seems to be the one currently blocking anything on top of it.
Do we really need master, that has some new dependencies indeed. kdelibs 4.7 
only requires 2.5.60, so some older stable release might be easier (no need 
for Raptor 2 there).

> kdelibs 4.7
> kdepimlibs master
> kdepim master
> kdepim-runtime master
> kdebase-runtime 4.7
> strigi (the one from komo branch) (unchanged)
> l10n trunk
> 
> Packaging rules will be:
> http://websvn.kde.org/branches/work/komo/packaging-master/
> 
> Buildlogs and such:
> http://saegewerk.intevation.de/buildlogs/details.py?treepkg=kdepim-mobile-fr
> emantle-trunk
> 
> Please help fixing the issues that occur, if you have any questions
> regarding the output of our packaging looks feel free to ask.
> Our build setup is quite simple, using treepackager (
> http://treepkg.wald.intevation.org/ )
> We basically just take the rules from one place, and update the checkout, If
> any of those changed a new build is triggered which happens in a scratchbox
> enviornment.
> The packages created in that build can then be used as dependency for other
> builds and so on.

Where would I change which Soprano branch is used? I guess that's something 
only you guys can do?

regards
Volker
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-mobile/attachments/20110827/983abf3b/attachment.sig>