Hi Tobias, On Do 25 Jan 2018 09:32:53 CET, Tobias Doerffel wrote:
Hi Mike, FYI: Veyon 4.0.4 is available at https://github.com/veyon/veyon/releases/tag/v4.0.4 I integrated the possibility to build without x11vnc builtin but instead use an external x11vnc binary (do not get confused that the plugin is still called "builtin-x11vnc.so" but it should be notably smaller). Simply pass -DVEYON_X11VNC_EXTERNAL=ON to cmake. No need for applying a patch. 2018-01-18 13:42 GMT+01:00 Mike Gabriel <sunwea...@debian.org>: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).Let me check the deps tree myself here. I'll get back to you on this.Any news? I still encourage you to keep things as they are as everything else will make things unnecessarily complicated for everyone without any notable benefit for the end user (except saving a few KB disk space in case KDE is installed vs. many MB disk space additionally in every other case). Best regards Tobias
I need some more feedback on the distribution of files over the various packages:
Package: veyon-master Package: veyon-service Package: veyon-configurator Package: libveyon-core And in debian/tmp I see these files directly after the build: ./usr/lib/x86_64-linux-gnu/veyon/powercontrol.so ./usr/lib/x86_64-linux-gnu/veyon/servicecontrol.so ./usr/lib/x86_64-linux-gnu/veyon/desktopservices.so ./usr/lib/x86_64-linux-gnu/veyon/localdata.so ./usr/lib/x86_64-linux-gnu/veyon/demo.so ./usr/lib/x86_64-linux-gnu/veyon/ldap.so ./usr/lib/x86_64-linux-gnu/veyon/linux-platform.so ./usr/lib/x86_64-linux-gnu/veyon/builtin-x11vnc-server.so ./usr/lib/x86_64-linux-gnu/veyon/textmessage.so ./usr/lib/x86_64-linux-gnu/veyon/screenlock.so ./usr/lib/x86_64-linux-gnu/veyon/config.so ./usr/lib/x86_64-linux-gnu/veyon/remoteaccess.so ./usr/lib/x86_64-linux-gnu/veyon/screenshot.so ./usr/share/icons/hicolor/scalable/apps/veyon-configurator.svg ./usr/share/icons/hicolor/scalable/apps/veyon-master.svg ./usr/share/icons/hicolor/48x48/apps/veyon-configurator.png ./usr/share/icons/hicolor/48x48/apps/veyon-master.png ./usr/share/pixmaps/veyon-configurator.xpm ./usr/share/pixmaps/veyon-master.xpm ./usr/share/polkit-1/actions/io.veyon.veyon-configurator.policy ./usr/share/applications/veyon-configurator.desktop ./usr/share/applications/veyon-master.desktop ./usr/bin/veyon-master ./usr/bin/veyon-ctl ./usr/bin/veyon-auth-helper ./usr/bin/veyon-configurator ./usr/bin/veyon-service ./usr/bin/veyon-workerHow shall I distribute these files over the above named packages? And: do I need another package (e.g. veyon-ctl or veyon-worker? Or a plugins package?).
Does it make sense to package plugins separately so that the site admin can add/remove features?
Mike -- mike gabriel aka sunweaver (Debian Developer) mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: sunwea...@debian.org, http://sunweavers.net
pgpt78c4_tdsk.pgp
Description: Digitale PGP-Signatur
