libkscreen without wayland backend and doctor.

[Baptiste Daroussin]

On Mon, Jan 23, 2017 at 01:49:32PM +0100, Tijl Coosemans wrote:
> On Mon, 23 Jan 2017 13:06:12 +0100 "Tobias C. Berner" <tcberner at freebsd.org> wrote:
> > On 23 January 2017 at 13:01, Tijl Coosemans <tijl at freebsd.org> wrote:
> >> On Sun, 22 Jan 2017 21:44:59 +0100 "Tobias C. Berner"
> >> <tcberner at freebsd.org> wrote:
> >>> On 22 January 2017 at 16:46, Tijl Coosemans <tijl at freebsd.org> wrote:
> >>>> On Thu, 19 Jan 2017 21:40:48 +0100 "Tobias C. Berner"
> >>>> <tcberner at freebsd.org> wrote:
> >>>>> On 19 January 2017 at 17:13, Jesper Schmitz Mouridsen
> >>>>> <jesper at schmitz.computer> wrote:  
> >>>>>> I've been working a little on LXQt (https://wiki.freebsd.org/LXQt)
> >>>>>> LXQt only misses plasma5-libkscreen in the offical portstree to
> >>>>>> build in the offical portstree.
> >>>>>>
> >>>>>> Therefore I patched plasma5-libkscreen [1] to build without wayland,
> >>>>>> e.g commenting out the wayland specific parts in CMakeLists and by
> >>>>>> skipping the "doctor" subdir. It builds and work with lxqt-config.
> >>>>>> Just want to know if there is an interest to have lib/libKF5Screen.so
> >>>>>> in the offical tree without wayland support?
> >>>>>>
> >>>>>> 1 http://lxqt-freebsd.schmitz.computer/ \
> >>>>>> plasma5-libkscreen-port-without-wayland.tar.gz
> >>>>>
> >>>>> I added a slightly modified version of your idea to the plasma5 branch
> >>>>> in r13609.
> >>>>>
> >>>>> I'm not quite sure if it is ideal to have just "bits" of plasma5 in the
> >>>>> ports tree, when we cannot provide the whole desktop -- which we can't
> >>>>> until wayland is in... But we should maybe think about it ^^
> >>>>
> >>>> If libkscreen is the only thing blocking LXQt it should definitely be
> >>>> added to the tree.
> >>>>
> >>>> Wayland on FreeBSD is still several months away I think so how critical
> >>>> is it for plasma5?  Surely it should work with a pure X11 system?
> >>>
> >>> plasma5 requires graphics/wayland [1] from [2] for the screenlocker
> >>> component for example -- even for X11 based sessions [3]. (So by the same
> >>> argument we could/should/have request[ed] graphics/wayland to be added to
> >>> the ports tree :P -- wayland may be months out, but that port has been
> >>> used for nearly two years now in the plasma5 branch).
> >>>
> >>> I'll create a diff for a patched plasma5-libkscreen for the ports tree.
> >>
> >> Is the graphics/wayland port the only thing you need?  Because that looks
> >> like a very simple component.  It should definitely be added to the tree
> >> if that's the only thing blocking plasma5, and then you don't need this
> >> libkscreen hack.
> >
> > yes :) -- I don't think we imported anything else into our plasma5 branch.
> 
> Bapt, can you look into (and commit) graphics/wayland?  It's the only
> thing blocking KDE5.

I finish upgrading the xorg server and yes I will have a look at it.

Best regards,
Bapt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-freebsd/attachments/20170123/7bc6aa12/attachment.sig>