> If you want to provide a patch, then you have to handle the Perl module > based code in the master branch, I guess. However, this is in the middle > of transition, currently.
Is master in a working state or temporarily broken? I'd rather like rebasing my code on top of master than building on soon-to-be-obsolete code. In what time scale do you expect to be finished with your refactoring? > No configure script, yet!!! >> ? The INSTALL file in that directory doesn't say something about >> "configure", but that's probably because it refers to the enduser that >> extracts x2goserver from a tar.gz file and not from the git repository. > > The enduser hopefully can install X2Go server from one of the available > distro archives... Installing via distro mechanisms requires root priviledges. Userspace installation must certainly be done via "configure --prefix=... && make && make install". If ever I come that far than the behaviour for the current (root) installation shouldn't be in any way any different. > If the configure file works for system-wide installations, then yes. Well, that goes without saying. > I guess, that you are aware that you have to test both cases (user space > X2Go and system-wide X2Go). What do you mean by "test"? I haven't yet found that 'make check' would be available inside the x2goserver directory. Ralf _______________________________________________ X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
