Moved these files into the same folder as the relevant source code.

I'm doing this so it's easier to see what's related to the new haxelib,
and what's related to the legacy haxelib.  I'll commit a shell script
soon which builds the server/ folder up as required
Added folder for legacy haxelib.

This is current Haxe SVN, + the changes required to get it to live
nicely inside the "legacy" subfolder.

I'll submit a patch for this to the haxe compiler team so it's updated
there too, but I thought it might be easier to keep it in our repo for
now.
Add compiling for legacy.  Add commands to site.sh to set up server/ folder
Updated htaccess to have new rules allowing redirects to /legacy/
Fixes to get site setting up correctly and compiling
Ignore server/ from the repo (as it is being built with site.sh now)
Changed Site / SiteApi to be separate neko files

The aim here is to have:

 * Site -> server/index.n (the web site, no remoting calls processed in this module^)
 * SiteApi -> server/api/2.0/index.n (accepts remoting calls)

(^) Note: Remoting calls sent to this URL though ("lib.haxe.org/") will be mod_rewrite forwarded
    to legacy/index.n

Any future backward-incompatible API changes should have a new API version number and endpoint.
Added (legacy haxelib) to the page title, so it's easier to know which is which
Merge branch 'master' into feature/legacysupport

Conflicts:
	src/tools/haxelib/SiteApi.hx
	src/tools/haxelib/website.mtt
Bump version number
If address is "/index.n" route to "/"
Moved new haxelib stuff into src folder, update site.sh to copy them

(So that it is easier to distinguish what is for legacy, what is for new)

(Feel free to undo this, but if you do, change where legacy assets go too)
Added legacy haxelib build.

Had to change import to get it to build too...
Update remoting redirect to use "legacy" not "haxelib1"
Change to point to my test server for now...
Make the DB writeable by the server
Make sure writeable files are set to o+w
More fiddling with permissions

 - server/ has to be writeable for sqlite file that lives in it
 - server/haxelib.db has to be writeable
 - server/tmp and server/files both have to be writeable
 - same for server/legacy

The entire folder being writeable sounds like a security issue to me...
but I guess not everyone runs on shared servers :)
Point them both to local servers for now
Realised TMP_DIR and REP_DIR both have to be in the web root

Because the existing haxelib tool uses straight HTTP for uploading and
downloading the zip files, our .htaccess redirect won't work.

The solution is to keep both in the top level directory, so:

 * I've adjusted legacy Site to point to ../files/
 * I've adjusted new Site to point to files/2.0/
 * I've adjusted site.sh to make sure 2.0 exists and is writeable

I figured we might as well keep the TMP_DIR shared if REP_DIR is,
so I've adjusted that also.