I have the following line in a script:
svn propset svn:externals $newExternals $path
Now for the first time
$newExternals is a multi-line string (there are several
svn:external properties) and
svn barks at me in a way that seems to indicate that it cannot deal with the argument.
Can I not pass a multi-line string to a program I invoke in PowerShell? Or is that a problem with
svn not being able to parse that? Or do I need quotes? (Didn't help, but I might have screwed up something else.)
If this doesn't work, then
svn would also accept a file to read the stuff from:
svn propset svn:externals -F externals.txt $path
However, this seems to fail because
externals.txt to be an ASCII file (or UTF-8, I'm not sure, but I don't think it's relevant here), while PowerShell by default writes UTF-16. So what's the canonical way to pipe something into an ASCII file?
As a side question: What's the canonical way to get a path to create a temporary file at?