[Pkg-x2go-devel] Bug#655618: ITP: nx-libs -- NX protocol libraries and binaries

[Reinhard Tartler]

clone 655618 -1
retitle 655618 ITP: nx-libs-light --- NX Protocol client-only libraries and binaries
retitle -1 ITP: nx-libs --- NX Protocol client/server libraries and binaries
stop

On Fr, Jan 13, 2012 at 10:20:15 (CET), Mike Gabriel wrote:

> Hi Paul, hi John,
>
> On Fr 13 Jan 2012 09:30:09 CET Paul van der Vlis wrote:
>
>> Op 13-01-12 02:22, John A. Sullivan III schreef:
>>
>>> As SPICE improves, I think we should consider it
>>> seriously.  Its cross platform support is very good which would no
>>> longer limit X2Go server to Windows only and the idea of an adaptive
>>> protocol is absolutely intriguing.  I long for the day we can
>>> realistically do video playing on the virtual desktop across a WAN.
>>
>> X2go-server is not Windows-only, it even does not run on Windows.
>> Not sure what you want to say.
>
> Note: we tend to get off-topic here. This thread is about packaging
> X2Go server / NX-libs for Debian. Please note by the To:/Cc: field,  how
> many lists/people are involved in this discussion.

I think the recipient list is appropriate. It includes everyone that
should discuss the inclusion of this software into the Debian Archive.

As some people raised concerns about including the x2go server into
Debian, I'm there splitting this ITP into two parts, following to the
way x2go provides its sources: At
http://code.x2go.org/releases/source/nx-libs/ two tarballs of nx-libs
are provided: one called 'lite' and one called 'full'. AFAIUI, the
'lite' tarball is a true subset of the 'full' tarball containing only
the parts that are relevant for building the client parts of the NX
stack. This is what bug #655618 is about from now on. The package is
being prepared at
http://anonscm.debian.org/gitweb/?p=collab-maint/x2go/nx-libs.git;a=tree
and, from what I see, is appropriate for being uploaded to unstable. For
clarity, I think we should rename the git repository from nx-libs.git to
nx-libs-light.git. Mike, can you please handle that?

For further discussion of the server parts (called "agent" in NX lingo),
which AFAIUI is a heavily patched fork of the old XNest codebase linked
against the Nomachine NX protocol libraries, please use the cloned bug.
I agree that without the blessing of the release team the security team,
it shouldn't go into unstable (or wheezy), but if the ftp-masters agree,
then I think it could go into experimental, so that interested parties
can start to have another serious look at it. If the project decides
that the server becomes suitable for inclusion into unstable, it will
then replace the 'nx-libs-light' package.

As I understand from Mike's other posting in this thread, there are
people looking at porting the agent to a newer codebase. But this is a
rarther long-term option. As are the suggestions to port x2go to SPICE.

As for the concerns with Nomachine, while it is true that NX 4.0 is no
longer GPL licensed, the 3.x codebase has seen updates, which maintain
its previous license, the GPLv3. I take this as indication that
Nomachine still has an interest in maintaining the 3.x codebase, which
included security fixes in the latest releases.

Cheers,
Reinhard

-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4