I have a kind of fundamental understanding question :/
Our nx package at the moment is built from the following upstream
tar balls:
-nxproxy
-nxcomp
-nxcompext
-nxssh
-nxcompshad
-nx-X11
-nxauth
-nxwin
-nxagent (x2go redistributed version)
-nxscripts
I only recently took the package over and used mainly the Mandriva
package and some things I borrowed from Fedora.
Are those parts (all of them are identical according to checksums on
nomachine and x2go download pages, but nxagent (which I took from x2go)
or don't exist on x2go download pages) the same as included in the
nx-libs tar ball?
So to really get x2go working (including x2goagent), is it neccessary to
change the whole nx package?
And will other tools using nx (like freenx, which I personally don't
know) still work?
If there should be any documentation about this, please point me to it,
I'm happy to read, but to be honest I don't find that much stuff to read.
If anyboday should be interested in how our nx package is built, the
spec file is available in our svn:
http://svnweb.mageia.org/packages/cauldron/nx/current/SPECS/nx.spec?view=markup
Thanks,
Oliver
_______________________________________________
X2Go-Dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/x2go-dev
