tags:

views:

82

answers:

1

This Subversion import command works on dos command line:

"C:\Program Files\Subversion\bin\svn.exe" import c:\myproj file:///c:/svnrepo/myproj -m "test"

If I try to send the same command with Rebol Call Command with this script:

Print "This command will and your files to the repository without requiring a working copy"    
repo-directory: to-local-file ask "repo: "
project-subdirectory: to-local-file ask "project: "
source-directory: to-local-file ask "source directory: "
comment: ask "comment: "
command: rejoin [{"} Subversion.Directory "bin\svn.exe" {"} " import " source-directory " file:///" (replace/all (to-local-file repo-directory) "\" "/") "/" project-subdirectory " -m " {"} comment {"}]
call/wait/console command

I will get this

repo: c:\svnrepo
project: myproj
source directory: c:\myproj
comment: test
svn: The given propagation message is a path (-F was this intended ?) ; force with 
 '--force-log'
== 1

The value of command is the same as the Dos command:

>> command
== {"C:\Program Files\Subversion\bin\svn.exe" import c:\myproj file:///c:/svnrepo/m
yproj -m "test"}
>>

So I appended --force-log and it did then work but I still would like to know the reason Rebol doesn't behave like Dos Command if there is one that I ignore.

+1  A: 

And if you write the command to say %script.cmd and call that from Rebol, do you get the desired effect?

Graham Chiu