Modify the block's character of yaml to avoid future problemsbaserock/OpenSSL_1_0_1g

When blocks of text are flowed with >, e.g.

    key: value
    foo: >
       The quick brown fox jumps
       over the lazy dog.

The new-lines of the text block are removed. This causes confusion
when shell scripts are involved, as the following Yaml would be
parsed as one shell command, rather than two:

    command: >
        echo foo bar
        ls

This escaped detection since if text is indented, Yaml treats it as
a different block, so

    command: >
        if true; then
            echo foo bar
        fi

is parsed correctly, but

    command: >
        if true; then
            echo foo bar
            ls
        fi

is not.

To avoid this confusion, we can always use `|`, which will preserve
the newlines, so an explicit continuation can be requested with a
`\` at the end of the line.

    command: |
        echo foo bar \
             baz quux

1 files changed, 1 insertions, 1 deletions

diff --git a/openssl-new.morph b/openssl-new.morph
index d92bba165d..2ed14ff248 100644
--- a/openssl-new.morph
+++ b/openssl-new.morph
@@ -3,7 +3,7 @@ kind: chunk
 max-jobs: 1
 configure-commands:
 - sed -i -e 's,^LIBNAMES=\\(.*\\) padlock \\(.*\\),LIBNAMES=\\1 \\2,g' engines/Makefile
-- >
+- |
   if [ "$(uname -m)" = "ppc64" ]; then
       sh ./Configure linux-ppc64 --openssldir=/etc/ssl --prefix="${PREFIX-/usr}" --libdir=lib shared
   else