Hi Mike, thank you very much for your efforts! I'll try to adopt as many of the changes as possible for the 4.1.6 release.
Regarding the package structure: everything looks fine so far. You could put veyon-ctl in a separate package but probably it's better to postpone this step until Veyon 4.2 has been released (where we'll rename veyon-ctl to veyon-cli which would lead to package renames and the first transitional packages). Do you plan to add transitional packages for existing iTALC installations so that users get migrated to Veyon automatically? Regarding libvncserver/libvncclient: I'm actively working with upstream to get all Veyon-specific changes merged in a generic manner so we can use an existing libvncclient library from the system. Currently the only thing left is to disable the broken (non thread-safe) IPv4 support in favor of the new (existing and generic) IPv6 code in libvncclient. Once libvncserver 0.9.12 is released and about to be packaged we could even solve this with a small Debian-specific patch. > Furthermore, here comes another request: how could we bring the Veyon > documentation files (as source files, as built Sphinx documentation) > into Debian? I'd say it makes sense having those docs packaged, so > they can be made available offline. As you probably already know the sources for the docs are available at https://github.com/veyon/docs and can be built via sphinx easily. For future releases I can create tags for the docs as well so you can simply download a tarball which can be used as source tarball for a separate veyon-docs package. Best regards Tobias
