Community
Participate
Working Groups
We currently have 5 "R builds" on our download page. I think 4 of them could be moved to "archive" server to reduce to load on mirrors, etc. R20090529135407 R20090825191606 R20100114021427 R20100519200754 I'll need to check, but think we have way to update repo URLs to "point to" archives? Just opening this now so I won't forget :)
For the record, each of our "R-builds" (well, any build probably :) takes about 400 M bytes. 349M ./R20090529135407/ 364M ./R20090825191606/ 365M ./R20100114021427/ 659M ./R20100519200754/ 434M ./R20110523182458/ The R20100519200754 is "extra large" because that's when we switched to providing the archive file for the repository, but we left the traditional "run time zip" there in case anyone needed it while transitioning.
Move those 4 builds to "archives" (actually, copied all 5, but left the most recent on downloads ... in future, technically, 20110523182458 can just be removed from downloads, no need to recopy). The only thing I could see that referred to 'download.eclipse.org' was the two map files that have URLs, such as orbitBundles-R20100519200754.map orbitBundles-R20100519200754.p2.map So, changed those to "archive.eclipse.org" with a script file. Just to document it, there is a script file that makes the "copy" and replacement semi automatic. It is contained under /home/data/httpd/archive.eclipse.org/tools/orbit/downloads/drops and just takes the build name as argument, such as ./archive.sh R20100519200754