On Wed, Jun 20, 2018 at 9:08 PM John Marino wrote:
>
> On 5/28/2018 08:35, Gerald Henriksen wrote:
> > On Thu, 24 May 2018 12:12:37 -0500, you wrote:
> >
> >>
> >> Just about every KDE5 except the top-level x11/kde5 metaport has been in
> >> dports for a few weeks already.
> >
> > Thanks for the
On 5/28/2018 08:35, Gerald Henriksen wrote:
On Thu, 24 May 2018 12:12:37 -0500, you wrote:
Just about every KDE5 except the top-level x11/kde5 metaport has been in
dports for a few weeks already.
Thanks for the reply and your work on dports
To follow up, the full KDE5 is blocked by
zrj and I got kd5-webengine working, so those ports will ultimately make it
into the repo. However, zrj says there's a big version update coming to
all the kd5 stuff so he's decided to integrate the webengine fixes into
that work. DragonFlyBSD will thus definitely see a working kd5-webengine
and
On Thu, 24 May 2018 12:12:37 -0500, you wrote:
>
>Just about every KDE5 except the top-level x11/kde5 metaport has been in
>dports for a few weeks already.
Thanks for the reply and your work on dports
On 5/24/2018 12:12, John Marino wrote:
On 5/24/2018 11:07, Gerald Henriksen wrote:
Now that KDE 5 has reached FreeBSD is there any timeline for it
arriving in DPorts.
Alternatively, what is the best way to try and build it that doesn't
interfere with it arriving in DPorts in the future
On 5/24/2018 11:07, Gerald Henriksen wrote:
Now that KDE 5 has reached FreeBSD is there any timeline for it
arriving in DPorts.
Alternatively, what is the best way to try and build it that doesn't
interfere with it arriving in DPorts in the future.
Just about every KDE5 except the top-level
Now that KDE 5 has reached FreeBSD is there any timeline for it
arriving in DPorts.
Alternatively, what is the best way to try and build it that doesn't
interfere with it arriving in DPorts in the future.
