On 25.08.2016 04:11 PM, James M. Pulver wrote:
Is this intended to eventually replace X2Go?
Depends on what you're asking about. Traditionally, we have been using nx-libs, a fork of the NX libraries as published by NoMachine (back then when they still released the source code.) Changes to that have been tracked via quilt and patches then applied to the tree. The source tree itself included a private X.Org Server copy, into which NX changes were hooked/written. The latest version was/is based on X.Org 6.9 from 2008.
When Arctica was created by Mike Gabriel and other developers of X2Go, the intend was to shift development focus within this (Arctica) project to nx-libs, to clean it up, make development easier by directly changing the source tree, update the source tree to the current X.Org Server version and splitting off NX-only changes so that eventually we have 2 clean subsets: an unmodified X.Org Server tree (which could then be easily discarded) and NX files as a separate DDX (driver.)
With this architecture, nxagent could be pushed upstream tot the X.Org Server repository and maintenance be carried out there - with more man power, providing a better integration, immediate fixes when something else within the X.Org Server core source changes.
Also, with that, we could *finally* get nx-libs into Debian and Debian-based distros, which currently deny accepting these packages due to the huge complexity, size and maintenance work currently required (think CVE fixes/backports and other security fixes) due to including a full, very old X.Org Server source tree.
The plan for X2Go is to switch to nx-libs 3.6 as provided by the Arctica Project with X2Go Server 4.1.0.0 (which is also why that has been so delayed.) Currently, nx-libs 3.6 isn't released yet either, we've had only a 3.5.99 release in July.
Otherwise, Arctica plans to provide a generic(!) framework for Remote Desktop applications in the distant future, of which X2Go can be one provider or plugin. This philosophy differs hugely from X2Go's, which aims to provide wrappers (CLI and GUI) above the NX libraries (and maybe RDP support in X2Go Client, too.)
Hence, Arctica will never supersede X2Go, but rather provide an infrastructure/framework *for* X2Go and other Remote Desktop providers.
Mihai