Menu
Is there any way to use Relative path when configuring subversion externals.
For example
Trunk - directoryA - directoryB - projectA {external DirectoryB} For configuring ProjectA we have to configure full path in the external property which is causing problems or forcing us to do change the properties when we do branches.
Any way to automate the branching process or fix with absolute path will be useful
813
Relative paths make use of two special symbols, a dot (.) and a double-dot (..), which translate into the current directory and the parent directory. Double dots are used for moving up in the hierarchy. A single dot represents the current directory itself.
As illustrated throughout this book, Subversion uses URLs to identify versioned resources in Subversion repositories. For the most part, these URLs use the standard syntax, allowing for server names and port numbers to be specified as part of the URL: $ svn checkout http://svn.example.com:9834/repos …
svn update brings changes from the repository into your working copy. If no revision is given, it brings your working copy up-to-date with the HEAD revision. Otherwise, it synchronizes the working copy to the revision given by the --revision option.
Subversion 1.5 clients support relative urls:
See the Subversion 1.5 release notes and the subversion manual for more details
Some examples: (Note that the comment syntax is not supported)
# Repository root relative ^/projectX/trunk/src/ projectX # Relative to current directory ../../dependency/X X # Server root relative /svn/repos/projectX/trunk/src projectX # Schema relative //svn.collab.net/repos/svn/trunk svn If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
