[X2Go-Dev] Reorganization of http://code.x2go.org/releases/

Michael DePaulo mikedep333 at gmail.com
Sun Sep 7 04:41:58 CEST 2014


Everyone,

I just did a reorganization of http://code.x2go.org/releases/

I would like to know:

1. Should we post this to our announcements list? Other projects might
be using specific URLs.
2. Who uploaded all these Windows builds on 2014-08-08?

Main changes:

1. There were a bunch of builds posted under these 2 folders on 2014-08-08:
http://code.x2go.org/releases/binary-win32/x2goclient/
http://code.x2go.org/releases/binary-win32/pyhoca-gui/
I moved them to subfolders such as:
http://code.x2go.org/releases/binary-win32/x2goclient/previews/3.99.2.1/
2. Some of those uploads were duplicates. I deleted the duplicates only.
3. I cleaned up the 3rd-party binary and sources directories. For
example, for libssh, windows builds are now under these folders:
http://code.x2go.org/releases/binary-win32/3rd-party/libssh/
http://code.x2go.org/releases/binary-win32/3rd-party/libssh-modified-by-x2go-project/
And libssh sources (including individual patch files) are under these folders:
http://code.x2go.org/releases/source/libssh/
http://code.x2go.org/releases/source/libssh-modified-by-x2go-project/

The general rules I have are:
1. If the source code (including makefiles) was modified by X2Go
project members, put the binaries and sources under
"-modified-by-x2go-project" folders, including under a subfolder if
you deem appropriate..
2. The 1st rule still applies if you expect the the patches to be upstreamed.
3. If they were not modified by X2Go project members, put them under
folders without that suffix, including under a subfolder if you deem
appropriate.
4. If all the patches were upstreamed, then new releases with all
those patches incorporated should be under a folder without that
suffix.

-Mike


More information about the x2go-dev mailing list