On Wed, Jun 25, 2014 at 9:48 AM, Michael DePaulo <[email protected]> wrote: > For the time being at least, there need to be multiple builds of X2Go > Client for Windows. You can read about them here: > http://www.x2go.org/doku.php/doc:release-notes-mswin:x2goclient-4.0.2.0#current_builds > > I suggest the following: > > Given a release like "4.0.2.0+build4": > http://code.x2go.org/releases/binary-win32/x2goclient/releases/4.0.2.0+build4/ > 1. I create a subdir called "other-builds" and put all the other builds in it. > 2. For all existing releases, I will move the other builds to that new > directory, but create a symlink from their current locations under > /binary-win32/x2goclient/tmp . > > I am open to suggestions for other names for the subdir. Perhaps > "non-default-builds"? > > And remember that releases such as "4.0.2.0+build4" are newer releases > of X2Go Client for windows, note separate builds, despite having > "build" in their name. They indicate though that the source code for > x2goclient has not been modified, only a bundled dependency (VcXsrv, > openssl, etc) has been updated. Usually I do not even rebuild > x2goclient.exe with them. > > -Mike
Also, I will not touch/move any of the "interims" "with-old-pulseaudio-0.9.6" builds that existed for 4.0.1.3+build2 and prior. -Mike#2 _______________________________________________ x2go-dev mailing list [email protected] http://lists.x2go.org/listinfo/x2go-dev
