Building master KDE PIM with Docker

[Daniel Vrátil]

Hi David,

you could try switching the "FROM" line (should be the first line) in the 
Dockerfile to "kdeneon/plasma:dev-unstable", maybe it will have newer stuff.

I guess the main problem is libical and too old Frameworks? In the worst case 
we can build libical as part of the Docker build and you can always build the 
latest Frameworks yourself by running "kdesrc-build frameworks" inside the 
container.

Dan



On Friday, 9 March 2018 18:53:03 CET David Jarvie wrote:
> I have followed the instructions at https://community.kde.org/KDE_PIM/Docker
> for building kdepim, but the Neon image (based on Ubuntu Xenial 16.04) is
> too old to provide the necessary dependencies. For example, it only
> provides libical 1.0, whereas master kdepim requires libical 2.0.
> 
> Is there a way to update Neon in the Docker container, to allow kdepim
> master to be built?


-- 
Daniel Vrátil
www.dvratil.cz | dvratil at kde.org
IRC: dvratil on Freenode (#kde, #kontact, #akonadi, #fedora-kde)

GPG Key: 0x4D69557AECB13683
Fingerprint: 0ABD FA55 A4E6 BEA9 9A83 EA97 4D69 557A ECB1 3683
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20180311/ba88ede2/attachment.sig>