I have been on looking around for the latest source and was unable to find anything other than SVN access, unfortunately I cannot access SVN (as in download) and downloading one file at a time from the http SVN is probably going to take as long as writing spring from scratch, are there any source packages that are updated more recently ? I cannot use smartSVN because it is Java, and I cannot use tortoisesvn because it's MSI and that requires a service pack which I do not and cannot have, isn't there an ftp/http link to compressed svn archives which are updated more recently ?
maybe you could put the archive of the latest SVN in http://www.osrts.info/~tvo/spring ?
getting latest source without SVN
Moderator: Moderators
-
monohouse
ok I found a good svn client and updated the page at http://taspring.clan-sy.com/wiki/Source ... the_Source but I would still prefer to download ftp/http and without additional programs.
-
monohouse
yes I did use it, but at the time I did not know there was one as your wiki did not mention a command client, now that I found it I updated the wiki page, but one of the biggest problems with svn is that it is most of the time broken and does not compile, it might be possible to have at the same time a compressed package of some version which does work and compile.
for example my recent encounters with version 3100 did not go so well, and I think this is only the beginning, I expect much more compile errors later on, and if not thanks to tobi for helping me I would be stuck a long way from that, spring code is very hard to compile
so I thought maybe there could be "compilable svn" as opposed to full released packages, they are not as updated as svn but could be updated on a daily basis, a kind of midpoint between full release and svn, thus it is both quite updated but it does not have the risk of not compiling.
for example my recent encounters with version 3100 did not go so well, and I think this is only the beginning, I expect much more compile errors later on, and if not thanks to tobi for helping me I would be stuck a long way from that, spring code is very hard to compile
so I thought maybe there could be "compilable svn" as opposed to full released packages, they are not as updated as svn but could be updated on a daily basis, a kind of midpoint between full release and svn, thus it is both quite updated but it does not have the risk of not compiling.
-
monohouse
actually, I do, but SVN is working, is it possible that I did not write it before because I think I wrote it 3 times already that my svn is working, I changed the topic now into why svn alone may not be optimal because it does not compile, but if the only way was to get svn is using Java or MSI then svn would not be working, so I still highly recommend to have a source package which is newer than the latest release, much like the bot that is used to compile and automatically put the packages that it managed to compile so that we know that it compiles and it can be used, becaues im having a serious trouble compiling the version 3100 and im sure that something like that would help alote for many reasons, it would also download like 10-20 times faster becaue it is compressed and because you download only one file.
-
monohouse
of corse not, I mean that tvo's http://www.osrts.info/~tvo/spring could in addition to compiling compress the SVN source that succeeded compilation and not compress the ones that did not succeed and thus have a working compilable package in addition to the automated build process also an automated packaging process IF compilation is successful, no manual things needed, and im sure if tvo was able to make a compile script for the svn there is no reason he could not make a compression script with it.
so yes an exact copy of the SVN but an exact copy of a WORKING and COMPILING SVN
so yes an exact copy of the SVN but an exact copy of a WORKING and COMPILING SVN
Last edited by monohouse on 09 Jan 2007, 16:09, edited 1 time in total.
-
monohouse
With a decent SVN client, there's an option to update to a certain revision (as opposed to updating to HEAD - the most recent revision). So you could look in the buildbot status page to see which revision was the last one to build correctly, and put that revision number in the proper field of your SVN client when updating, so it updates to that revision.
-
monohouse