Under http://debian.tu-bs.de/knoppix/nx/freenx-0.2.6.tar.gz ther is a new freenx version. Is someone working on a version bump?
And 0.27. Is there ever going to be action on this?
Created attachment 45848 [details]
This is the latest 1.4.0 NX libraries
Created attachment 45849 [details]
This is the latest nxclient 1.4.0 ebuild
Created attachment 45850 [details]
This is the latest nxproxy ebuild
Created attachment 45851 [details]
This is the latest nxssh ebuild
Created attachment 45852 [details]
This is the latest freenx ebuild
Created attachment 45853 [details, diff]
Fixes path for nxserver-freenx
This patches nxserver to have the correct path for nxnode-login.
Sorry - there's only the one of me, and other packages have had to take priority for the last month or so. I'll bump this package as soon as I have some time.
Christian, in future please attach ebuilds as text/plain. Thanks for the work, though.
meta-fied this bug :)
The NX Client ebuild is broken. Nomachine have moved their binaries around and changed the paths.
P.S Why is the Server depending on the binary client (or any client for that matter) anyway? It doesn't need the client to run.
The commercial NX Server *does* need the NX Client, unless something has changed very recently.
Perhaps the commercial one does depend on the nx-client binaries, but nxserver-freenx shouldn't because otherwise it prevents you from building a non-binary/fully open source installation with this technology. Gentoo is supposed to be about choices after all and NX is allegedly GPL at its core.
Gentoo is all about choice. But equally it's about quality - and that means doing our best to ensure that the packages that go into Portage have the right deps.
The architecture of the nxserver relies on nxclient to display key dialog boxes. It's the nxclient installed on the same machine as the nxserver which displays these dialog boxes - not the nxclient on the machine that you are connecting from.
I'll have a look at freenx 0.2.7, and see if it provides a drop-in replacement for nxclient. If it does, and if it works, then we can use that. If not, then the dep on the commercial nxclient will have to remain.
That explains the 'nxclient' shell script in the FreeNX distribution. It's just enough to do the dialog servicing required by the server.
The nxclient shell script uses the binary nxclient, Xdialog and xmessage in order of preference to display dialogs.
Hopefully at some point it will allow the use of the kNX client as well.
*** Bug 71522 has been marked as a duplicate of this bug. ***
*** Bug 70928 has been marked as a duplicate of this bug. ***
I've committed version bumps for nx-x11 et al to Portage, based on Christian's attachments. They should appear on your local rsync mirror in about an hour. Please test, and let me know how you get on.
Initial test results reported as new bug
Closing old bug