using SVN to download a stable version
Moderator: Forum Moderators
using SVN to download a stable version
Is it possible to use a SVN to download a stable version?
For example, last stable version is 1.6.4. Changelog is http:// svn.gna.org/viewcvs/wesnoth/tags/1.6.4/players_changelog?rev=36631&view=download
Is rev=36631 means that SVN version 36631 is 1.6.4 version?
If I give
It says that is 1.7... version...
For example, last stable version is 1.6.4. Changelog is http:// svn.gna.org/viewcvs/wesnoth/tags/1.6.4/players_changelog?rev=36631&view=download
Is rev=36631 means that SVN version 36631 is 1.6.4 version?
If I give
Code: Select all
svn update -r 36631 http://svn.gna.org/svn/wesnoth/trunk wesnoth
Re: using SVN to download a stable version
Yes it is. But you have to keep in mind that SVN is a strange system that copies older versions elsewhere in the tree. So if you download the "trunk" part of the tree, you will necessarily get the trunk version. If you want 1.6, you should point svn to "branches/1.6" or "tags/1.6.4" instead. No need to use a revision number by the way.vvb wrote:Is it possible to use a SVN to download a stable version?
Re: using SVN to download a stable version
Well, don't use trunk if you really want tags/1.6.4.
or if you want to switch from a trunk checkout for example:
Code: Select all
svn checkout http://svn.gna.org/svn/wesnoth/tags/1.6.4
Code: Select all
svn switch http://svn.gna.org/svn/wesnoth/tags/1.6.4
"If gameplay requires it, they can be made to live on Venus." -- scott
Re: using SVN to download a stable version
The main idea is to decrease traffic.
If I keep updating trunk SVN and use "svn switch" everytime stable release is come out, will it be efficient?
If I keep updating trunk SVN and use "svn switch" everytime stable release is come out, will it be efficient?
Re: using SVN to download a stable version
Yes. It'll only download/update the files which differ between those two branches. When you switch your trunk checkout to for example 1.8 after 1.8 has been released, there's going to be very few changes.vvb wrote:The main idea is to decrease traffic.
If I keep updating trunk SVN and use "svn switch" everytime stable release is come out, will it be efficient?
Re: using SVN to download a stable version
zookeeper wrote:Yes. It'll only download/update the files which differ between those two branches.
The main idea was to decrease traffic.
I've give command:
Code: Select all
svn switch http://svn.gna.org/svn/wesnoth/tags/1.6.4 wesnoth
Re: using SVN to download a stable version
That revision does not exist on trunk so you weren't on it if you're switching from trunk. By now I guess there are quite some differences between 1.6 and 1.7 so if you want to follow both with minimal traffic you need to have checkouts for both.vvb wrote:I thought that 36631 was closest revision to 1.6.4... but it still updating and updating... keeps downloading more and more...
"If gameplay requires it, they can be made to live on Venus." -- scott
Re: using SVN to download a stable version
Soliton wrote:... if you want to follow both with minimal traffic you need to have checkouts for both.
Well... I had trunk SVN (36631). After command
Code: Select all
svn switch http://svn.gna.org/svn/wesnoth/tags/1.6.4 wesnoth
If next stable release will come out (say, 1.6.5). Which command should I use to update 1.6.4 to 1.6.5?
Re: using SVN to download a stable version
vvb wrote: If next stable release will come out (say, 1.6.5). Which command should I use to update 1.6.4 to 1.6.5?
Code: Select all
svn switch http://svn.gna.org/svn/wesnoth/tags/1.6.5
"If gameplay requires it, they can be made to live on Venus." -- scott
Re: using SVN to download a stable version
Every revision "exists on trunk" ... or, better said, there is a trunk directory tree in every revision.Soliton wrote:That revision does not exist on trunk so you weren't on it if you're switching from trunk.vvb wrote:I thought that 36631 was closest revision to 1.6.4... but it still updating and updating... keeps downloading more and more...
It may be the same as the revision before, when this revision did not change anything on trunk, but it exits.