Building master KDE PIM with Docker

[David Jarvie]

Hi Dan,

I tried kdeneon/plasma:dev-unstable, but that doesn't fix things.

Martin's question about why we need the libical 2.0 dependency prompted me to 
try changing back to depending on libical 1.0 in my build tree. This builds 
ok, so it looks like libical is the only missing kdepim dependency in the Neon 
docker container. For now, I'll just carry on using libical 1.0 - it's easier 
than building a libical 2.0 package.

Cheers,
David.

On Sunday 11 Mar 2018 22:02:36 Daniel Vrátil wrote:
> 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?

-- 
David Jarvie.
KDE developer.
KAlarm author -- http://www.astrojar.org.uk/kalarm