I'm using 'net-misc/qtnx' to access 'net-misc/nxserver-freenx'. So I have no need for 'net-misc/nxclient'. Maybe the 'net-misc/nxserver-freenx' ebuild should replace "nxclient? (net-misc/nxclient)" by "nxclient? (||(net-misc/nxclient net-misc/qtnx))". By the way, is there a really a need for this flag ? If someone wants a server and a client, can't he just emerge both ? More importantly, why is this flag on by default? If so, well since 'net-misc/nxserver-freenx' is the opensource version of the nx server, at least an opensource client such as 'net-misc/qtnx' should be an option in the dependencies.
net-misc/nxserver-freenx:nxclient - Allow to install net-misc/nxclient in parallel with this package, using it to display messages in the sessions freenx needs a helper program to display some messages, for exemple the "Terminate and disconnect" dialog when closing a NX full session window. It works better with nxclient itself (mimicking closed-source NX servers calls), and with USE=-nxclient, it uses xdialog/xmessage as a replacement. Last time I checked qtnx did not implement this xdialog part, mostly focusing on the "real" client code. So this why the current ebuilds are set-up this way: nxclient recommended by upstream, xdialog/xmessage as a fallback
Thanks for the explanation. I guess I can close the bug now (disabling the flag and adding qtnx to my portage world will do the job for now).
