I have to believe so, but was a tad daunted when I tried to start using the SVN::Alien suite. It is huge and there appears to be little documentation on how to do the basics with it.
I am an SVN Padawan Learner. Take care, Chris -----Original Message----- From: Markus Schaber [mailto:m.scha...@3s-software.com] Sent: Monday, May 23, 2011 11:05 PM To: Varnau, Steve (Neoview); users@subversion.apache.org Subject: AW: SVN question Hi, Steve, Maybe one of the libsvn bindings for perl does a better service than calling the command line utility? Best regards Markus Schaber ___________________________ We software Automation. 3S-Smart Software Solutions GmbH Markus Schaber | Developer Memminger Str. 151 | 87439 Kempten | Germany | Tel. +49-831-54031-0 | Fax +49-831-54031-50 Email: m.scha...@3s-software.com | Web: http://www.3s-software.com CoDeSys internet forum: http://forum.3s-software.com Download CoDeSys sample projects: http://www.3s-software.com/index.shtml?sample_projects Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915 Von: Hahn, Christopher (SAN DIEGO) [mailto:christopher.h...@hp.com] Gesendet: Montag, 23. Mai 2011 22:54 An: Varnau, Steve (Neoview); users@subversion.apache.org Betreff: RE: SVN question 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 successful exit code. The way around that is the odd “-s” switch which causes the tool to emit a string like “exit: #” where the underlying commands success or failure was specified. Is there perhaps some similar technique for SVN? 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) Sent: Monday, May 23, 2011 1:33 PM To: Hahn, Christopher (SAN DIEGO); users@subversion.apache.org Subject: RE: SVN question 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) Sent: Monday, May 23, 2011 11:34 AM To: users@subversion.apache.org Subject: SVN question Hello, I have been wondering how best to capture errors from the SVN command line. I wanted to show you how a basic test is failing. Consider the simple code snippet: ========================================== use strict; my $options=" --username builduser --password XXXX"; chdir("C:\\source"); my $output = `svn update --depth=infinity mang $options`; die "svn failed with errorcode $?" if $?; print "We survived!\n"; ========================================== This command works if the “mang” above is changed to “main” (which does exist at c:\source). However, both code have this result: ========================================== C:\source\cm\script>perl svntest.pl We survived! C:\source\cm\script>perl svntest.pl We survived! ========================================== What am I doing wrong? Chris ________________________________________ Christopher Hahn The Dude Software Production Engineering R&D Services, Hewlett-Packard Phone: 858-655-4096 Cell: 619-630-9791 ch...@hp.com Visit our SPE Portal ________________________________________
