<div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> > If you want to get all files you only have to do a svn export<br>> > <a href="http://vtiger.fosslabs.com/svn/vtiger/vtigercrm/branches/5.0.3/./$LOCALDI">
http://vtiger.fosslabs.com/svn/vtiger/vtigercrm/branches/5.0.3/./$LOCALDI</a><br>> >RECTORY<br>><br>> Is this how you use it ?<br><br>No. I use:<br><br>svn<br>diff --old=<a href="http://vtiger.fosslabs.com/svn/vtiger/vtigercrm/branches/5.0.3/@$OLDRELEASE">
http://vtiger.fosslabs.com/svn/vtiger/vtigercrm/branches/5.0.3/@$OLDRELEASE</a> --new=<a href="http://vtiger.fosslabs.com/svn/vtiger/vtigercrm/branches/5.0.3/@HEAD">http://vtiger.fosslabs.com/svn/vtiger/vtigercrm/branches/5.0.3/@HEAD
</a><br><br>And patch it by hand. Then you look for DB changes and change the database if<br>needed.<br><br>> It should be as simple as a "svn update", even between branches, shouldn't<br>> it ?<br>No.
</blockquote><div><br>Ok, based on my experience with other projects, I know for a fact that it is possible to keep your local modifications and benefit from svn updates without having to create patches between versions.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>> Because of changes in the structure of the source between the checked out
<br>><br>> > source and the deployment you have to build a diff if you want to update<br>> > a working deployment and update by "patch".<br>><br>> Well, svn should deal with the change on the source, that's its job.
<br><br>But your deployment differs with the source.</blockquote><div><br>Yes, but again it shouldn't be a problem. Can we imagine two seconds a use case scenario ?<br><br>I've fixed a bug on the 5.0.2 and there is a new
5.0.3 version. I want to use it, but, of course, to be sure my patch is still existing.<br>They are three scenarios:<br>1) The bug is still on the 5.0.3 (and my fix still work)<br>2) They have applied it as offered and I need to "forget" my patch
<br>3) They have fixed it, but with a different patch than what I submited<br><br>Only the last case should need my intervention. I expect the SCM to deal with the others smoothly. <br><br>I think the problem is that you are expected to change your working branches for every minor version. In other OSS softwares, the main versions (
4.2, 5 and 5.1) are branched before the dev, and the minor ones after (as mainstones while producing the patches, new tar distos).<br><br>ie. you always work in the same branch 5.n for all its live and you only svn update, and have to branch only when you go from
5.0 and 5.1.<br><br>I mentioned something like that a few months ago, would it be possible to consider it or am I the only one thinking that would be saving a lot of time without any additional problem ?<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Look at:<br><a href="http://vtiger.fosslabs.com/svn/vtiger/vtigercrm/branches/5.0.3/schema/DatabaseSchema.xml">http://vtiger.fosslabs.com/svn/vtiger/vtigercrm/branches/5.0.3/schema/DatabaseSchema.xml</a></blockquote><div>
<br>Brilliant, thanks. Could you recommend a way of using these to generate mysql commands with the diffs ?<br></div><br>X+<br></div>