Hi,
I have created a life cycle management application for my custom content. I use sub-version as my vms repository.The LCM application is configured to use only one sub-version account (vms/vms) for all its activities.All the content that exists in my respository are binary content.
I have run into some issues and need your input.
Q1. Non-linear editing of versionsI have a binary content (eg: A report) that has Ver. 1,2,3. I checkout V2 do some editing and checkin the report.however i do not see V4. How do i do it?
List of commands being used:
Add Resource:
This is a combination of three commands,
svn add $1 $2 $1- path of the resource to be added. (In all the cases below, it refers to the location of the resource in the workspace)
svn commit $1 –m “$2” $1- path of the resource to be added.$2 – message to be passed by the user.
svn update $1 $1- path of the resource to be updated.
Checkin resource:
svn commit $1 –m “$2”
Get latest revision:
svn update $1
Get revision:
svn update $1 --revision $2
$1- path of the resource to be updated$2- the revision number of the resource that is to be obtained
Get file history:
svn log $1 –xml –verbose $1- the repository URL location of the resource.
Checkout a workspace(done for the first time):
svn checkout $1 $2 –N $3
$1- the repository URL location of the resource.$2- workspace path of the resource.$3- authorization parameters.
Get workspace revision:
svn status $1 –xml –verbose $1- workspace path of the resource.
Q2. Is subversion lock smart enough to understand that checkout has occured from 2 machines using the same account, can it warn the user?
_________________________________________________________________
Watch hottest Bollywood videos, clips, movie tailors, star interviews, songs and more on MSN videos.
http://video.msn.com/?mkt=en-in
Received on 2008-05-30 05:19:35 CEST