NX 3.3 branch packages, it's your turn!
Candidate packages are:
* net-misc/nxcl-0.9-r1 (new use flag to work with standard ssh)
Are there any restrictions as to which ones need to be marked stable together?
I can stabilize nxnode, nxclient, and nxserver-freeedition. I'm not sure if freenx can co-exist with the freeedition server, and I think that plain nx requires a license to use? Is it ok to mark just the three stable until somebody else can test the rest? I didn't see any dependency issues with the other packages, but...
Yes for stabilization you can do these 3 at the same time. nxserver-freeedition ebuild installs its license automatically
The relations between all ebuilds are as follow:
* nxnode, nxclient, and nxserver-freeedition form the "closed-source" ensemble, better to stable major versions at the same time
* nxserver-freenx works with all nxclient versions (or even without, if using xmessage), and any net-misc/nx, I just usually ask for nxserver-freenx and net-misc/nx stabling at the same time as they form the GPL version of NX (net-misc/nx is just the GPL parts of NX, the server itself is in freenx and does not need a license)
* nxcl and qtnx form the GPL client, and do not depend on specific versions of other NX packages either
So in short, no problem if you stable the freeedition, freenx can wait ;)
nxclient, nxnode, and nxserver-freeedition are amd64 stable
The GPL versions still require stabilization. If nobody else picks them up in a week I'll see if I can back up my current configuration and test them out.
amd64/x86 stable, all arches done.