Yes, it is a sucky situation.
It's basically chromium, and needs patches, lots and lots of patches, as
none of the BSDs are supported.
See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212817#c1 for some
On 20 September 2016 at 18:11, Dwayne MacKinnon <d...@ncf.ca> wrote:
> Ouch. That might be a show-stopper for me. I use kmail a *lot*.
> Out of curiosity, what's the issue with Qt5WebEngine? It doesn't do
> anything silly like depend on systemd does it?
> ----- Original Message -----
> From: "Tobias C. Berner" <tcber...@freebsd.org>
> To: "d...@ncf.ca d...@ncf.ca" <d...@ncf.ca>
> Cc: "Tobias" <tcber...@freebsd.org>, "Adriaan" <gr...@kde.org>, "KDE" <
> Sent: Tuesday, September 20, 2016 11:36:27 AM
> Subject: Re: getting started with KF5
> Hi there
> Unfortunately kdepim-16.* requires Qt5WebEngine. So it cannot be built at
> moment on FreeBSD.
> On the other hand kdepim-4* conflicts with components installed by the
> Desktop. So it cannot be installed either.
> In short: at the moment, you cannot have a KDE Pim Suite.
> I have ~100 patches locally to make it build against Qt5WebKit again, which
> turn let's it be installed again. However, one of the reasons WebEngine was
> chosen upstream to replace WebKit was security. So I'm not quite sure,
> patches are really the "right" thing to do. Also they need more work =)
> mfg Tobias
> On 20 September 2016 at 06:24, Dwayne MacKinnon <d...@ncf.ca> wrote:
> > Hi all,
> > Decided to give kf5 a go on my system. I was wondering, do I have to go
> > back to kdepim4? I get a message that the new akonadi needs
> > which hasn't been ported yet.
> > Thanks,
> > DMK
> > On Sep 19, 2016 3:14 AM, "Tobias C. Berner" <tcber...@freebsd.org>
> > Hi
> > On 19 September 2016 at 00:54, Adriaan de Groot <gr...@kde.org> wrote:
> > On Monday 19 September 2016 08:45:39 Graham Menhennitt wrote:
> > > Hi all,
> > >
> > > I'm new to this and would like to test some KF5 stuff. I'm running
> > > FreeBSD stable-11 on AMD64. Could somebody please tell me how to get
> > > started.
> > >
> > > I know that I have to get the SVN repo from area51. But what's the next
> > > step? Do I copy that over the top of a standard ports repo? Or do I
> > > to merge things somehow? And then what - "cd /usr/ports/x11/kde; make"?
> > - Get area51. Get the plasma5/ branch, because it's where the current
> > state-
> > of-the-art lives.
> > - (optional) get a separate ports checkout somewhere
> > - in the plasma5/ checkout, run
> > $ sh Tools/scripts/kdemerge -a /path/to/ports
> > This will merge all the KDE area51 ports into that ports tree (which
> > why
> > you might want to use a separate ports checkout, so it's easy to undo).
> > - For the biggest effect, build x11/kde5
> > - It might be good to switch off your display manager (if you have one
> > already
> > on your FreeBSD system) and using startx for a bit. You probably just
> > exec /usr/local/bin/startkde in .xinitrc (note that the plasma5 branch
> > shuffles
> > some KDE4 ports around, and what used to be startkde becomes startkde4).
> > There are also packages provided by swills@ which might be the fastest
> > way to
> > give it a go:
> > There is a script to add the repo here [if I picked the right one]:
> > https://gist.github.com/swills/8a9a9f8a529256f134830c2a1476db0c
> > or you can of course also manually add/modify a repo.conf.
> > > Is there a list of what I can expect to work and what won't?
> > I think tcb uses plasma5 on FreeBSD as his primary desktop, so "most"
> > things
> > apparently work. I've got to admit to sticking with KDE4 desktop, mostly
> > out
> > of inertia.
> > Indeed I do :) -- things mostly seem to work.
> > [ade]
> > mfg Tobias