In preparation for other software (like opennx for example), several ebuilds are needed for binaries, that are currently only available through the nst-misc/nxclient package. For example, nxssh and nxesd are open source. They can be downloaded here: http://www.nomachine.com/sources.php Reproducible: Always Steps to Reproduce:
Ah, another one intersted in opennx :) That's still in my TODO list, here is the current "state". indeed, nxssh/nxesd... are not in net-misc/nx, which only installs the open-source components needed for server side As opennx also depends on some parts that are in net-misc/nx, we could either: * add client/server USE flags to net-misc and keep one single package (easier but uglier) * split nx in (temp names) nx-common, nx-server, nx-client (with the last one blocking binary nxclient probably) * split in nx-common, nx-server, and opennx (which would install nxssh, nxed, ... as current binary nxclient does) Would be nice to have: in opennx, make cups, opensc, libsmb, pulseaudio optional , make it work with our cups setup (cups is not executable by normal users) Reassigning to nx to keep track of this, help is always welcome ;)
(In reply to comment #1) > Ah, another one intersted in opennx :) That's still in my TODO list, here is > the current "state". > > indeed, nxssh/nxesd... are not in net-misc/nx, which only installs the > open-source components needed for server side > > As opennx also depends on some parts that are in net-misc/nx, we could either: > * add client/server USE flags to net-misc and keep one single package (easier > but uglier) > * split nx in (temp names) nx-common, nx-server, nx-client (with the last one > blocking binary nxclient probably) I like this one. I wonder, whether one could/should remove all the components that are available as open source from the binary nxclient. Not sure, whether that will cause problems. I wonder, whether the cleanest solution would be to have individual ebuilds for all nx* packages. However, so far their makefiles sucks and I think I even saw some paths like "../nxfoo/" in the Makefiles. I wondered, whether that was the reason for the net-misc/nx ebuild. If I had some free time, I wanted to study the current ebuilds and actually divide them up into individual ones. Is that welcome? What about the directory structure? I noticed that some libraries were installed to /usr/lib64/NX/lib64 (which seems to be a very odd path). Other were installed to /usr/NX/lib64 (which looks better to me, for no real reason). Are there any rules for what goes where? Do you know any distro that already has nx packages? I could copy their directory structure. But I didn't find any :-( > * split in nx-common, nx-server, and opennx (which would install nxssh, nxed, > ... as current binary nxclient does) > > Would be nice to have: in opennx, make cups, opensc, libsmb, pulseaudio > optional , make it work with our cups setup (cups is not executable by normal > users) Hmmm. I have a very simple opennx ebuild. It doesn't really have any of the features you ask for and does very bad things to reach its goal. I try to clean it up, and post it here when it's ready.
Cleaning old bugs opennx (and most nx projects) have gone away in the meantime, we will see how the artica project will end up doing packaging (though single nx/nx-libs package seems to be the idea)