[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#887394: Packaging Veyon (was: Re: Accepted italc 1:3.0.3+dfsg1-2 (source) into unstable)



Hi Mike,


2018-01-18 12:38 GMT+01:00 Mike Gabriel <sunweaver@debian.org>:
> My main issue with the packaging is the 3rdparty/ folder. I know that iTALC
> had embedded code, too, and that you maintain it thoroughly. What's the
> status of that with Veyon.

The same here.


> Is there any chance to use Debian unstable's versions of those 3rdparty
> libs?

Partially, see below.


> Also, what of those dependencies are tightly compiled into Veyon?
>
>   1. I guess ultravnc is for the Windows build, only, is it?

Yes, it's not used for Linux builds.


>   2. Can kldap be used from Debian?

Theoretically this would work however this would introduce a strong
dependency on KDE while Veyon uses only a small part of the kldap
library without any dependencies on KDE at all. Veyon's LDAP support
plugin uses some (Qt-based) core classes of kldap but none of it's
KDE-specific model and widget classes. For all non-KDE users this
would unnecessarily install many KDE libraries and make them think
Veyon is a KDE program (which it isn't).


>   3. Can libvncserver be used from Debian?

Inside libvncserver there are two libraries: libvncclient and
libvncserver. We have to use a customized version of libvncclient in
order to implement our own authentication schema. This means the
libraries from the libvncclient1 package are not compatible with Veyon
and the 3rdparty version has to be used. The libvncserver1 package is
only required by x11vnc so this all depends on how we deal with
x11vnc:


>   4. Can x11vnc be used from Debian (my sense here is not)?

In Veyon we use a builtin version of x11vnc, i.e. call the main entry
point directly where needed. With iTALC we also extended x11vnc with
our protocol extensions. With Veyon the Veyon server acts as a VNC
proxy, filters out and handles Veyon-specific traffic and thus can use
an unmodified VNC server as a backend. This means I could provide a
patch which optionally builds the VNC server plugin without x11vnc
builtin but calls an external x11vnc process.

Best regards

Tobias


Reply to: