RE: SVN question
From: Varnau, Steve (Neoview) <steve.varnau_at_hp.com>
Date: Mon, 23 May 2011 21:30:26 +0000
svn does not always return success. For instance:
> svn ls
I think this is the more normal mode that I script against. I'm not sure why the update sub-command is so forgiving.
-Steve
From: Hahn, Christopher (SAN DIEGO)
Steve,
Thank you for taking the time.
I also saw this....I was wondering what users do to get something similar working.
The same thing happens under Perforce. The command "p4" always returns a
I checked the svn Global Options and did not see anything similar.
I suppose that I can just use a pipe and watch for strings that I expect.....
Take care,
Christopher
From: Varnau, Steve (Neoview)
Christopher,
The problem is not with your perl code. Apparently, update returns success if you give it a path that does not exist in the current working directory.
Ø svn update foobar
At revision 3158.
Ø echo $?
0
For Svn 1.6.15, anyway. Seems to hold for linux & windows.
-Steve
From: Hahn, Christopher (SAN DIEGO)
Hello,
I have been wondering how best to capture errors from
I wanted to show you how a basic test is failing.
Consider the simple code snippet:
chdir("C:\\source");
die "svn failed with errorcode $?" if $?;
This command works if the "mang" above is changed to "main"
However, both code have this result:
C:\source\cm\script>perl svntest.pl
What am I doing wrong?
Chris
________________________________
[cid:image001.png_at_01CAF080.AD65F1E0]
Christopher Hahn
Visit our SPE Portal<http://teams5.sharepoint.hp.com/teams/SPE/default.aspx>
________________________________
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.