[Pkg-x2go-devel] [X2go-dev] Starting to get x2go into Ubuntu Oneiric

[Stéphane Graber]

Oops, I can understand the confusion :)

Yes, I meant nxproxy, not nxagent.
I'd indeed expect x2goagent to have a lot more changes than the
libraries but it already has a different name, so it'll just be
completely different package in the archive.

I'm currently only focusing on getting python-x2go in the Ubuntu archive
and its two depends are:
 - nxproxy
 - nxcomp

So that's what I'm working on.

Anything that's currently called "x2go*" should be uploaded using that
as source package name and binary package name, even if an equivalent
exists at NoMachine.

The question is for:
 - nxcomp
 - nxcompext
 - nxcompshad
 - nxproxy

As these are still active on NoMachine's side and don't seem to contain
a lot of delta on x2go's side (at least for nxcomp and nxproxy).

If x2go is going to break the API for these, then they need to be
renamed to a x2go* equivalent so we can have both NoMachine's and X2go's
version in the archive at the same time.

That said, so far I haven't found any indication of an API-breaking
change on x2go's side so I'd instead recommend having x2go maintain a
standard patchset on top of NoMachine's version that packagers can
easily pull in their packages.

As a quick status update, I now have done an initial package for nxcomp.
I'll be rebuild nxproxy using that new nxcomp and then will be testing
them both this afternoon. If the result is satisfying (works as expected
with x2goclient, python-x2go and qtnx) I'll be uploading these two to
Ubuntu Oneiric and will send the patches to x2go-dev and pkg-x2go-devel
for merging.

Thanks


-- 
Stéphane Graber
Ubuntu developer
http://www.ubuntu.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-x2go-devel/attachments/20110520/a74fbb6d/attachment.pgp>