Perhaps I am wrong, but to my humble understanding, nxcomp is compiled as a part of nx-x11.
If that is so indeed, why is there a dependancy of both nx-x11 and nxcomp for nxserver-freenx?
Steps to Reproduce:
nxcomp isn't explicitly listed as a dependency in any of the nxserver-freenx ebuilds. Also, Portage doesn't show nxcomp in the dependency tree either:
emerge --tree --emptytree --pretend -vD nxserver-freenx | grep net-misc
[ebuild N ] net-misc/nxserver-freenx-0.2.7 0 kB
[ebuild N ] net-misc/nxclient-1.4.0-r3 0 kB
[ebuild N ] net-misc/nxproxy-1.4.0-r2 0 kB
[ebuild N ] net-misc/nx-x11-1.4.0-r3 0 kB
I think you fixed it in your local portage tree.
On the formal Gentoo tree, the latest ebuild for freenx is nxserver-freenx-0.2.4
Could you please add the new ebuilds to the portage tree?
Also, nxcomp appears in the dependencies, altough it is included in nx-x11.
This is the output I got:
lightstar ~ # emerge --tree --emptytree --pretend -vD nxserver-freenx | grep net-misc
[ebuild N ] net-misc/nxserver-freenx-0.2.4 0 kB
[ebuild N ] net-misc/nxclient-1.3.2-r1 0 kB
[ebuild N ] net-misc/nxssh-1.4.0 -ipv6 -kerberos +pam +tcpd 0 kB
[ebuild N ] net-misc/nxproxy-1.3.2 0 kB
[ebuild N ] net-misc/nxcomp-1.4.0 0 kB
[ebuild N ] net-misc/nx-x11-1.4.0-r2 0 kB
lightstar ~ #
nxserver-freenx-0.2.4 is no longer in the Portage tree. It was replaced by nxserver-freenx-0.2.7 earlier this morning.
It may take an hour for the changes to propagate to your local rsync mirror.